From 8d0ec50095ff1a30066d08a06d568c436a6cf5a5 Mon Sep 17 00:00:00 2001 From: Ayaz Salikhov Date: Sun, 21 Jan 2024 15:29:27 +0400 Subject: [PATCH] Improve wording --- docs/using/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using/troubleshooting.md b/docs/using/troubleshooting.md index 70483c3981..d9497ed27c 100644 --- a/docs/using/troubleshooting.md +++ b/docs/using/troubleshooting.md @@ -84,7 +84,7 @@ The following sections cover a few of these scenarios and how to fix them. Docker handles mounting host directories differently from mounting volumes, even though the syntax is essentially the same (i.e. `-v`). - When you initialize a Docker container using the flag `-v`, the host directories are bind-mounted directly into the container. + When you initialize a Docker container using the `-v`flag, the host directories are bind-mounted directly into the container. Therefore, the permissions and ownership are copied over and will be **the same** as the ones in your local host (including user ids) which may result in permissions errors when trying to access directories or create/modify files inside.