SwarmSpawner Persistence of user notebook directories error
See original GitHub issueI use add the lines below in jupyterhub_config.py:
notebook_dir = os.environ.get('DOCKER_NOTEBOOK_DIR') or '/home/jovyan/work' c.DockerSpawner.notebook_dir = notebook_dir c.DockerSpawner.volumes = { 'jupyterhub-user-{username}': notebook_dir }
It is use to persist user notebook directories. And got an error:
Incompatible options have been provided for the bind
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (1 by maintainers)
Top Results From Across the Web
DockerSpawner API - Read the Docs
The user sees a file listing of this directory when the notebook interface is started. The current interface does not easily allow browsing...
Read more >jupyterhub/jupyterhub - Gitter
Hi all, I am using JupyterHub to start docker containers using DockerSpawner. I want a directory in there to be automatically mounted to...
Read more >Spawn failed for user after jupyterhub restart, received signal ...
spawn failed for user after jupyterhub restart, log shows. received signal 15, stopping SingleUserLabApp notebookapp:2052] Shutting down 0 kernels
Read more >JupyterHub Documentation - Read the Docs
level directory users will be able to access in the notebook dashboard. ... JupyterHub 0.8 adds the ability to persist state related to ......
Read more >Deploying Jupyter Notebooks at scale on XSEDE resources ...
Finally, we can configure SwarmSpawner so that the first time a user requests a Jupyter Notebook, a Docker. Volume is created as a...
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
I spent a lot of time to resolve issue with not working volumes with SwamSpawner. Finally I resolved it by:
I know it is workaround but is only way to attach user directory in SwarmSpawner mode.
@sangramga Thanks for replying! I tryed it, but still got the error. After reading the code of SwarmSpawner, I found that maybe there may be a problem here:
But our type is “bind” here.