plasma icon indicating copy to clipboard operation
plasma copied to clipboard

Published 20 hours ago • verified publisher icon plasmabio

Server options not showing environments

Open lachlancampbell opened this issue 4 years ago • 4 comments

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 https://github.com/jupyterhub/jupyterhub/issues/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.

lachlancampbell avatar Feb 02 '21 10:02 lachlancampbell

Thanks @lachlancampbell for reporting.

Error: DockerError(400, 'no such image: None: invalid reference format: repository name must be lowercase'

Out of curiosity, what does the name of the environment look like? It could be that tljh-repo2docker didn't sanitize it correctly.

jtpio avatar Feb 09 '21 07:02 jtpio

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.

lachlancampbell avatar Feb 09 '21 08:02 lachlancampbell

@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.

  1. I've succeeded in creating 3 environments using the templates which all work with binder:

environment_screen

  1. But users don't see the environments when they log in:

spawn_screen

  1. And instead the plugin gives them the non-existent jupyterhub/singleuser:1.1 environment

admin_screen

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 avatar Jun 27 '21 17:06 phaustin

:wave: @phaustin sorry for the delay. Did you go into the Permissions tab to set the visibility of your environments to the group your user belongs to?

pierrepo avatar Nov 09 '21 21:11 pierrepo