Docker-stacks: Volume Mounting via Docs Not Working with User Joyvan

[nandanrao]

Using jupter/scipy-notebook

From fresh Ubuntu 16.04 run docker command (as user ubuntu, uid 1000):

docker run -d -v /home/ubuntu/work:/home/joyvan/work -p 8888:8888 jupyter/scipy-notebook start-notebook.sh --NotebookApp.token=''

Exec into the docker container to find the following, the image has created a new /home/joyvan/work directory under the root user!

jovyan@c45fec83bd1e:~/work$ cd /home
jovyan@c45fec83bd1e:/home$ ls -l
total 8
drwxr-xr-x 1 jovyan users 4096 Jan 27 13:05 jovyan
drwxr-xr-x 3 root   root  4096 Jan 27 13:05 joyvan

According to the docs, I was expecting this to mount a volume from my host machine into the /work directory that the Jupyter notebook uses as its work directory.

[DrPaulBrewer]

Check spelling it is jovyan

On Jan 27, 2017 8:13 AM, "Nandan Rao" [e-mail] wrote:

Using jupter/scipy-notebook

From fresh Ubuntu 16.04 run docker command (as user ubuntu, uid 1000):

docker run -d -v /home/ubuntu/work:/home/joyvan/work -p 8888:8888 jupyter/scipy-notebook start-notebook.sh --NotebookApp.token=''

Exec into the docker container to find the following, the image has
created a new /home/joyvan/work directory under the root user!

jovyan@c45fec83bd1e:~/work$ cd /home
jovyan@c45fec83bd1e:/home$ ls -l
total 8
drwxr-xr-x 1 jovyan users 4096 Jan 27 13:05 jovyan
drwxr-xr-x 3 root root 4096 Jan 27 13:05 joyvan

According to the docs, I was expecting this to mount a volume from my host
machine into the /work directory that the Jupyter notebook uses as its work
directory.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jupyter/docker-stacks/issues/332, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUUSBt8fOVWMoHG-VWc-RvThOcLmiB-ks5rWe16gaJpZM4LvwEl
.

[nandanrao]

lol. well, shiiiiiiiiiiiiiiiit, my bad.

[pmbaumgartner]

I don't know if this is an issue, but is there some logic behind the user name? I ran into this exact same issue today. Yes, user error, yada yada, but if its preventable frustration for future users to switch to an identifiable/relevant name (conda / jupyter / jupyter-docker), then that would reduce this issue.

[entmike]

lol. well, shiiiiiiiiiiiiiiiit, my bad.

Same thing happened to me today. I keep reading jovyan and joyvan. Lost 30 minutes of productivity on this LOL.

[Defunctionalize]

oh my god. I've spent months on this. I was sure the problem was some combination of Docker for Windows and using WSL (and then later in desperation WSL2) to interface with the containers.

Nope. just spelled it wrong. I hope someone finds this comment and judges me.