envs_dirs not respected when creating an environment #14027
Labels
pending::feedback
indicates we are waiting on feedback from the user
source::community
catch-all for issues filed by community members
type::bug
describes erroneous operation, use severity::* to classify the type
Checklist
What happened?
This issue is similar to #13453, but this bug is distinct from the issue described there. I recognize that
~/.conda/envs
is always going to be added toconda info
andconda config --show
, no matter what yourenvs_dirs
config entries look like in your.condarc
file(s).However, even when another location is specified and writeable (in this case
/opt/miniforge/envs
), conda no longer respects that specified location, and will create all new environments in~/.conda/envs
unless the--prefix
option is used. This appears to also apply to the CONDA_ENVS_PATH environment variable.This is contrary to the documentation for
envs_dirs
, which states:Conda Info
Conda Config
Conda list
Additional Context
I have noted this issue in both conda==
23.11.0
and conda==24.5.0
. This issue does not occur with conda==23.3.1
. All setups used the same exact directory structure, permissions, ACLs, etcs.The text was updated successfully, but these errors were encountered: