-
Notifications
You must be signed in to change notification settings - Fork 305
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
start.sh usermod and kubespawner mount volumes in home #574
Comments
It sounds like this needs to be managed in your container, not KubeSpawner: |
This is a discussion related to jupyter/docker-stacks. My understanding is that you discuss the following feature summarized.
I would overall say that this is a quite uncommon action, and could easily lead to loss of data if misunderstood by someone. Due to that, I'm not so happy about the idea of supporting a feature like that - if I understood it correctly. |
Oh... I couldn't transfer this issue to jupyter/docker-stacks as it was outside the organization. Anyhow, that is where this belongs. You could perhaps copy paste things from this to there if you want to raise it for discussion? Please if so, also include my response. |
@djangoliv If you mounted |
I am using base-notebook
In jupyterhub_config.py I add a volume:
So kubspawner creates the '/home/{username}' directory before running start.sh
In start.sh: After the
usermod
that changesjovyan
to{username}
there is a copy of/home/jovyan
to/home/{username}
but only if/home/{username}
does not yet exist.But with the volume, the home of
{username}
already exists and the copy does not happen.Maybe we can force the copy with an environment variable (
$COPY_HOME
) and not test if the home already exists.Any suggestions are welcome.
Regards
The text was updated successfully, but these errors were encountered: