-
Notifications
You must be signed in to change notification settings - Fork 12
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
Server options not showing environments #187
Comments
Thanks @lachlancampbell for reporting.
Out of curiosity, what does the name of the environment look like? It could be that |
I think it was "plain-python". I don't think it was the name though, as I used an image of my working VM to create a new one, and tried importing and it showed up fine in the environments. I've since deleted it, but I could try and replicate it. I did confirm that the PAM error occurs on my working hub, so not related. |
@jtpio -- I'm seeing similar symptoms, not sure whether it is a related problem or not. I'm happy to open up my digital ocean droplet where this is currently running.
Plasma is exactly what we're looking for at UBC for pangeo-ready jupyterhubs -- happy to do whatever it takes to get this working. |
👋 @phaustin sorry for the delay. |
Hi, I've had a working Plasma instance running on an Openstack cloud for several months with no problems. Yesterday I created a new instance and successfully ran the playbooks to create a new hub. The new hub will not allow a user server to be started - Error: DockerError(400, 'no such image: None: invalid reference format: repository name must be lowercase'). I'm assuming this is because the Server Options page (/hub/spawn) is not showing any of my environments, so I can't select them. I also did a quick check of the logs and it showed a PAM login error (similar to jupyterhub/jupyterhub#2754). I'm also assuming this behaviour is due to an update to TLJH or jupyterhub itself, as my old Plasma hub is still working fine.
The text was updated successfully, but these errors were encountered: