Skip to content
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

Make sure there's no ${HOME}/.conda dir #604

Open
yuvipanda opened this issue Mar 4, 2019 · 0 comments
Open

Make sure there's no ${HOME}/.conda dir #604

yuvipanda opened this issue Mar 4, 2019 · 0 comments
Labels

Comments

@yuvipanda
Copy link
Collaborator

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.

yuvipanda added a commit to yuvipanda/repo2docker that referenced this issue Mar 4, 2019
yuvipanda added a commit to minrk/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
@choldgraf choldgraf added the bug label Mar 4, 2019
markmo pushed a commit to markmo/repo2docker that referenced this issue Jan 22, 2021
conda sometimes puts stuff in $HOME - specifically under .conda/ -
that might cause package installs to fail due to permission mismatches.

Ref jupyterhub#604
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants