-
Notifications
You must be signed in to change notification settings - Fork 67
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
Stop unconditionally setting cmd
to jupyterhub-singleuser
#3434
Comments
jupyterhub/kubespawner#493 (comment) has related discussion summarized. I think the role of So, unsetting it is probably fine for all images that use |
Currently z2jh's default is to set More details on the understanding I have currently is reflected in the PR description for #3797. |
fwiw we still definitely do it in basehub:
|
@consideRatio can this be closed now? I remember you took some actions here, but I'm not sure what. |
I don't advocate any action related to this issue, so if you think its OK to close lets close! Logs etc is resolved, but we have via z2jh set singleuser.cmd explicitly, which I think we should. |
@consideRatio as long as you don't think we need to actively make any changes, I'm all good! Thanks for closing. |
in
basehub/values.yaml
, we setcmd
tojupyterhub-singleuser
, to account for images that may not have that correctly set up. However, this means that theENTRYPOINT
set up in the docker image is not run, causing issues with logging when using repo2docker (#3433) as well as startup when using desktop-proxy.We should evaluate if this is actually still needed, and if not, unset
jupyterhub-singleuser
ascmd
inbasehub/values.yaml
The text was updated successfully, but these errors were encountered: