-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 / 404 error on using docker spawner #23
Comments
Aha! I found a trace in the log:
|
What's your JupyterHub config? Which authenticator are you using for JupyterHub? |
I'm using the sample GitHub OAuth authenticator. https://gist.github.com/yuvipanda/08e06376ddb98f21a8c4 is the config. It works now after I fiddled around a bit - I set the ip address explicitly in the config, and also rebuilt the standalone docker container. Unsure which fixed it. |
I suspect setting the IP address explicitly in the config is what fixed it -- because the hub passes it's IP address along to the containers so they can communicate with the hub. The default is Anyway, glad you were able to fix it! |
Yup, containers are not run with --net=host, so that won't work. Thanks! |
Thanks @jhamrick !, I had the same problem when I launched the jupyterHub service. But now, I have my JupyterHub running 👍 . First, I executed the ifconfig command in the host, after that, I only had to change the line 'c.JupyterHub.hub_ip' with my ip and run again. |
I happen to stuck with this even after changing |
I can confirm the behavioru @anaderi is seeing: any containers need to be removed. |
Hello!
(First, thanks for the awesome work!)
I'm trying to set up a publicly accessible jupyterhub setup on Wikimedia Labs (jupyter.wmflabs.org). Would like to use docker to provide isolation as well as resource quotas / clustering (later on). Jupyterhub works with the default spawner, but with dockerspawner I get a '500 server error' when I click 'my server'. And if I ssh tunnel through and hit the proxied docker endpoint directly, I get a 404. No errors in jupyterhub stdout, so I'm not sure what's happening.
Thoughts?
The text was updated successfully, but these errors were encountered: