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
Currently, when installing miniconda we end up with a ${HOME}/.conda directory, with an environments.txt file. This is apparently to help sysadmins on multi user systems discover all the environments users have created on the system (from conda/conda#6748 (comment)). We don't really need that inside a container...
Having ~/.conda present causes problems when REPO_DIR isn't $HOME, since we then don't explicitly recursively chown it.
The text was updated successfully, but these errors were encountered:
yuvipanda
added a commit
to yuvipanda/repo2docker
that referenced
this issue
Mar 4, 2019
conda sometimes puts stuff in $HOME - specifically under .conda/ -
that might cause package installs to fail due to permission mismatches.
Ref jupyterhub#604
conda sometimes puts stuff in $HOME - specifically under .conda/ -
that might cause package installs to fail due to permission mismatches.
Ref jupyterhub#604
Currently, when installing miniconda we end up with a ${HOME}/.conda directory, with an environments.txt file. This is apparently to help sysadmins on multi user systems discover all the environments users have created on the system (from conda/conda#6748 (comment)). We don't really need that inside a container...
Having ~/.conda present causes problems when REPO_DIR isn't $HOME, since we then don't explicitly recursively chown it.
The text was updated successfully, but these errors were encountered: