mamba-org
Making mamba self-contained/Having user configured ~/.conda and ~/.condarc alternatives
Troubleshooting docs
My problem is not solved in the Troubleshooting docs
How did you install Mamba?
Micromamba
Search tried in issue tracker
self contained
Latest version of Mamba
My problem is not solved with the latest version
Tried in Conda?
Not applicable
Describe your issue
I need to use python and environment/package managers across different clusters with a shared home directory. With this in mind, I need a tool that is truly self contained and doesn't use files/directories inside the home directory. I know that I can make a symlink for ~/.conda to point somewhere else, but doing this means that I can't use micromamba on multiple clusters simultaneously.
~/.condarc
I've been able to override the use of the ~/.condarc file by making a .mombarc file located in ${MAMBA_ROOT_PREFIX}/.mambarc and removing the .condarc file in the home directory.
~/.conda/
Unfortunately I can't seem to find a similar solution to changing the location of where the .conda directory is located. Is there any solution to keep using a .conda directory with the environments.txt while specifying it be in another location (such as ${MAMBA_ROOT_PREFIX}/.conda/) ?
Solutions?
It would be really helpful if there was some user_home variable that could be configured to change where these files and directories are search for. Alternatively, being able to select an option to store them in ${MAMBA_ROOT_PREFIX} would truly make mamba/micromamba self contained.
Hi, you could try setting CONDARC environment variable to point to the config where you'd like.
Yes - I tried that! Unfortunately the issue isn't really in the rc file, since that can be moved and mamba will find it inside ${MAMBA_ROOT_PREFIX}/. The issue is the more in the ~/.conda folder, as it is always in the home directory, and it is automatically created whenever a new environment is created.
What do you see in the ~/.conda folder ? I'm not super familiar with it.