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
Describe the bug
If a person attempts to open Jupyter from within an ldmx image (dev or pro), they are prevented because the directories we add to specific jupyter environment variables are not write-able.
Expected behavior
We can avoid this error by not setting these environment variables.
A workaround is to edit the file at <denv workspace>/.profile to unset these variables.
denv true # make sure profile is copied over
cat >> .profile <<PROF
# unset errorneously set variables that should not be used since ROOT
# is installed in a read-only location
unset JUPYTER_CONFIG_DIR
unset JUPYTER_PATH
PROF
What tag of the container are you using? What application are you using to run the container?
Both of these are answered by denv config print.
denv_workspace="/export/scratch/users/eichl008"
denv_name="eichl008"
denv_image="ldmx/pro:v4.0.1"
denv_mounts=""
denv_shell="/bin/bash -i"
denv_network="true"
apptainer version 1.3.5-1.el8
The text was updated successfully, but these errors were encountered:
Describe the bug
If a person attempts to open Jupyter from within an ldmx image (dev or pro), they are prevented because the directories we add to specific jupyter environment variables are not write-able.
Error:
Location where this is set:
docker/Dockerfile
Lines 226 to 227 in 1c729e2
To Reproduce
Steps to reproduce the behavior:
denv init ldmx/dev:latest
denv python3 -m pip install jupyterlab
denv jupyter lab
Expected behavior
We can avoid this error by not setting these environment variables.
A workaround is to edit the file at
<denv workspace>/.profile
to unset these variables.What tag of the container are you using? What application are you using to run the container?
Both of these are answered by
denv config print
.The text was updated successfully, but these errors were encountered: