hazza/docker-stacks
1
0
Fork 0
mirror of https://github.com/jupyter/docker-stacks.git synced 2025-10-17 15:02:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1606 from he7d3r/patch-1

Browse Source 
Fix typo
This commit is contained in:
Ayaz Salikhov
2022-02-05 21:47:57 +03:00
committed by GitHub
parent 9a5700a431 4f8bbc2f96
commit 087274e796
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/using/troubleshooting.md
View File

@@ -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 <UID>` and `--group-add users` flags instead of `-e NB_UID` and `-e NB_GID`: