c.DockerSpawner.notebook_dir not working with JupyterHub 0.8
See original GitHub issueHi,
I am following this repo to setup my JupyterHub instance on a single server.
Recently, the repo was upgraded to JupyterHub 0.8 and I followed the changes. However, since the upgrade, the parameter c.DockerSpawner.notebook_dir
doesn’t seem to have an effect and the single user servers are always started at /home/jovyan
instead of /home/jovyan/work
I tried giving different values to the configuration param but it always starts at home directory.
I rollbacked my system to old code before the changes made in last few days and it worked again.
Any help is appreciated.
Thanks, Bhopesh
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Changes in DockerSpawner
DockerSpawner.hub_ip_connect is deprecated when running with JupyterHub 0.8. Use JupyterHub.hub_connect_ip instead, which is used by all Spawners.
Read more >SwarmSpawner fails on spawn notebook servers
I am using a `JupyterHub` deployment with `SwarmSpawner`. When I try to login, `JupyterHub` fails spawning the new container. I have the debug...
Read more >How To: Change the default start directory for Jupyter Notebook
Temporarily start Jupyter Notebook in a different directory using the ... NotebookApp.notebook dir = r'C:\Users\User\Desktop\Work\test'.
Read more >After updating JupyterHub 0.8.1 to 1.3.0.Not able to spawn ...
Docker images created should spawn without issues with network type as “host” with jupyterhub version :1.3.0.
Read more >Deploying a containerized JupyterHub server with Docker
These are nothing else than the Jupyter notebook servers you are used to run on your personal computer, however they are started and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s not why, it’s how. By default, DockerSpawner builds the command to launch the docker image from config such as
c.DockerSpawner.cmd
,c.DockerSpawner.ip
, etc. There are also some options that allow you to bypass any logic in DockerSpawner, and talk directly to Docker.extra_create_kwargs
is one such option. By specifyingextra_create_kwargs.command
, you are saying that you have decided what the command to launch should be, and that DockerSpawner should not try to build thecommand
itself.I figured a fix by trial and error but I don’t know why my fix is working. There’s some problem with the
start-singleuser.sh
script.Removing following two lines from
jupyterhub_config.py
starts the single user notebook servers at/home/jovyan/work
, otherwise single user notebook servers always start at/home/jovyan
irrespective of value ofc.DockerSpawner.notebook_dir
.Lines to be removed from
jupyterhub_config.py