I have authentication running on my BinderHub, my question is what to do about the following message? This seems to be occurring when a user is launching Binder instances in quick succession, but I feel like the user should be able to leave the Binder homepage open after they’ve authenticated and keep relaunching a Binder should they choose, or a different Binder repo. At the minute, they would have to wait for the culler to kill their user pod before they could open another Binder instance, or stop their server from the Control Panel in the Notebook environment (depending on the setting of
cull.users, I’ve tried playing with True and False values). Any advice?
Found built image, launching... Launching server... Launch attempt 1 failed, retrying... Launch attempt 2 failed, retrying... Launch attempt 3 failed, retrying... User <username> already has a running server.
config: BinderHub: use_registry: true image_prefix: <image-prefix>- hub_url: http://<jupyter-ip> auth_enabled: true jupyterhub: cull: users: false every: 660 timeout: 600 maxAge: 21600 hub: services: binder: oauth_redirect_uri: "http://<binder-ip>/oauth_callback" oauth_client_id: "binder-oauth-client-test" extraConfig: hub_extra: | c.JupyterHub.redirect_to_server = False binder: | from kubespawner import KubeSpawner class BinderSpawner(KubeSpawner): def start(self): if 'image' in self.user_options: # binder service sets the image spec via user options self.image = self.user_options['image'] return super().start() c.JupyterHub.spawner_class = BinderSpawner singleuser: cmd: jupyterhub-singleuser auth: type: github github: clientId: "<redacted>" clientSecret: "<redacted>" callbackUrl: "http://<jupyter-ip>/hub/oauth_callback"