`.mambarc`/`.condarc` being ignored?
See original GitHub issueI have a .mambarc
which specifies only the conda-forge
channel but when building with boa
packages were being installed from pkgs/main
.
I copied my /opt/micromamba/.mambarc
to /opt/micromamba/.condarc
but without any luck. What did work was copying /opt/micromamba/.mambarc
to ~/.condarc
(copying to ~/.mambarc
also didn’t seem to work).
So, I think there are two (probably related) issues here:
boa
seems to only support.condarc
and not.mambarc
boa
seems to ignore a.condarc
in$MAMBA_ROOT_PREFIX
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
micromamba seems to ignore default channel in environment
Conda does define a default channel though (which micromamba does not). The easiest way around this is to create a ~/.condarc or ~/.mambarc...
Read more >Configuration - Mamba's documentation! - Read the Docs
The configuration is parsed/read from multiple sources types: rc file: a file using YAML syntax. environment variable: a key/value pair set prior to...
Read more >Mamba 0.15.0 - Wolf Vollprecht - Medium
Micromamba (the pure C++ implementation of mamba) is gearing up for interactive use — it now has condarc / mambarc file reading in...
Read more >Using the .condarc conda configuration file
condarc , is an optional runtime configuration file that allows advanced users to configure various aspects of conda, such as which channels it...
Read more >How to modify the location of .condarc file? - Stack Overflow
The problem I am facing is that it is ignoring the envs_dirs variable is ignored, and it continues to select the one in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I believe that we were indeed relying upon a system config, rather than user, in the scenario that I was outlining in #265 - though it’s been a while! Also seems to be true for at least the first reply there, from someone else experiencing it. I do think that this is probably the same issue.
Probably best if I close #265, rather than you closing this one, as I think your report is more accurate and succinct.
I think this issue also impacts the creation of new environments from an environment.yml that specifies boa as a dependency. In my base environment
mamba info
reports:Exactly as I would expect. However, if I create a new environment (
mamba create -f environment.yml
) based on an environment.yml that containsthen inside of that environment
mamba info
reports:If I don’t list boa as a dependency in environment.yml then the resulting environment only includes the conda-forge channels like I would expect. I can also manually install boa in to one of these environments and conda-forge remains the only active channel.
The only way I’ve been able to include boa as a dependency in environment.yml and keep conda-forge as the only channel in the new environment is to copy .condarc, which only lists the conda-forge channels, from my system mambaforge install to ~/ before creating the new environment.