I cannot access the mounted home volume and a second volume that I mounted. This is the output of ls -al in a terminal within the started notebook.
jovyan@localhost:~$ ls -al
total 20
drwxrwxr-x. 6 jovyan users 61 Mar 29 12:42 .
drwxr-xr-x. 3 root root 20 Mar 7 15:10 ..
-rw-rw-r--. 1 jovyan users 220 Apr 4 2018 .bash_logout
-rw-rw-r--. 1 jovyan users 3770 Mar 7 15:10 .bashrc
drwxr-xr-x. 3 jovyan users 18 Mar 29 12:42 .cache
drwsrwsr-x. 2 jovyan users 30 Mar 17 21:11 .conda
drwsrws---. 3 jovyan users 25 Mar 17 21:21 .config
drwxr-xr-x. 5 nobody nogroup 4096 Mar 27 17:41 datahdd
drwsrwsr-x. 2 jovyan users 6 Mar 17 21:18 .empty
drwx------. 9 root root 4096 Mar 28 18:25 home
drwsrws---. 2 jovyan users 40 Mar 17 21:21 .jupyter
drwxr-xr-x. 3 jovyan users 39 Mar 29 12:42 .local
-rw-rw-r--. 1 jovyan users 807 Apr 4 2018 .profile
drwsrwsr-x. 2 jovyan users 6 Mar 7 15:10 work
One could enable root access via GRANT_SUDO=yes. But then users should know about this. Since I am dealing with students, that are completely new to the subject of programming and using computers, this is not an option. The easiest solution would be to not use jovyan at all. Then we could mount /home/USER of the host to /home/USER in the container.
With this solution we won´t need to write a separate routine for the moving of certs.
I cannot access the mounted home volume and a second volume that I mounted. This is the output of
ls -alin a terminal within the started notebook.One could enable root access via
GRANT_SUDO=yes. But then users should know about this. Since I am dealing with students, that are completely new to the subject of programming and using computers, this is not an option. The easiest solution would be to not use jovyan at all. Then we could mount /home/USER of the host to /home/USER in the container.With this solution we won´t need to write a separate routine for the moving of certs.