From 4f8bbc2f9677ed8b1a1f5a53c24cd4d57d265b23 Mon Sep 17 00:00:00 2001 From: Helder Geovane Gomes de Lima Date: Sat, 5 Feb 2022 14:37:15 -0300 Subject: [PATCH] Fix typo --- docs/using/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/using/troubleshooting.md b/docs/using/troubleshooting.md index c36a16b2..9e789254 100644 --- a/docs/using/troubleshooting.md +++ b/docs/using/troubleshooting.md @@ -86,7 +86,7 @@ The following sections cover a few of these scenarios and how to fix them. (including user ids) which may result in permissions errors when trying to access directories or create/modify files inside. Suppose your local user has a `UID` and `GID` of `1234` and `5678`, respectively. To fix the UID discrepancies between your local directories and the container's - directories, you can run the container with an explicit `NB_UID` and `NB_GID` to match the that of the local user: + directories, you can run the container with an explicit `NB_UID` and `NB_GID` to match that of the local user: ```bash docker run -it --rm \ @@ -202,7 +202,7 @@ If you have also **created a new user**, you might be experiencing any of the fo ``` This example uses the syntax `$(PWD)`, which is replaced with the full path to the current directory at runtime. The destination - path should also be an absolute path starting with a `/` such as `home/jovyan/work`. + path should also be an absolute path starting with a `/` such as `/home/jovyan/work`. - You might want to consider using the Docker native `--user ` and `--group-add users` flags instead of `-e NB_UID` and `-e NB_GID`: