You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting a container from JupyterHub, the chown -R operation takes too long if there are many files, leading to a timeout even though the timeout is already set to 600 seconds. The script enforces ownership changes when NB_UID and NB_GID differ from the defaults, causing significant delays.
your config/jupyter/start_notebook.sh:
# This script runs in local Jupyterlab only (e.g. Docker, Neurodeskapp)
# This script does NOT run on stock JupterHub/BinderHub instances (e.g. kubernetes)
# For global startup script, see ./config/jupyter/jupterlab_startup.sh
if [ -z "$GRANT_SUDO" ]; then
export GRANT_SUDO='yes'
fi
if [ -z "$RESTARTABLE" ]; then
export RESTARTABLE='yes'
fi
if [[ "$NB_UID" != "1000" || "$NB_GID" != "100" ]]; then
if [ -z "$CHOWN_HOME" ]; then
export CHOWN_HOME='yes'
fi
if [ -z "$CHOWN_HOME_OPTS" ]; then
export CHOWN_HOME_OPTS='-R'
fi
fi
Logs show that chown -R runs on /home/jovyan:
docker logs jupyterhub-5fnv
Entered start.sh with args: start-notebook.py
Running hooks in: /usr/local/bin/start-notebook.d as uid: 0 gid: 0
Sourcing shell script: /usr/local/bin/start-notebook.d/start_notebook.sh
Done running hooks in: /usr/local/bin/start-notebook.d
Update jovyan's UID:GID to 1013:1014
userdel: group jovyan not removed because it is not the primary group of user jovyan.
Ensuring /home/jovyan is owned by 1013:1014 (chown options: -R)
Do you know how to prevent this while still being able to change guid and uid for users with a lot of files in /home/joyvan?
The text was updated successfully, but these errors were encountered:
Apply the chown only when there is an actual mismatch between home dir and nb uid/gid. Currently it's hardcoded to expect 1000:100
The notebook will need the home directory and certain files and sub-directories to have the proper ownership to start up.
We could the startup script only modify those locations, instead of the entire home subtree. It might be the case that the user will need to manage the remaining files. Or have that moved to an extra flag
When starting a container from JupyterHub, the
chown -R
operation takes too long if there are many files, leading to a timeout even though the timeout is already set to 600 seconds. The script enforces ownership changes whenNB_UID
andNB_GID
differ from the defaults, causing significant delays.your config/jupyter/start_notebook.sh:
Logs show that
chown -R
runs on/home/jovyan
:Do you know how to prevent this while still being able to change guid and uid for users with a lot of files in /home/joyvan?
The text was updated successfully, but these errors were encountered: