Troubleshootings with conda¶
Activation fails¶
CondaError: Run 'conda init' before 'conda activate'¶
If you get the conda error: CondaError: Run 'conda init' before 'conda activate', please use source activate <my-env> instead of conda activate <my-env> command.
activate: No such file or directory¶
If you get the bash error: activate: No such file or directory, please load the conda module:
module load devel/Miniforge/Miniforge3
The base environment is always active¶
If you installed your own copy of conda, you may have this issue.
When opening a terminal, conda loads by default an environment named base.
As it can interfere with other software, we recommend disabling its automatic activation:
# We load the miniconda modulemodule load devel/Miniforge/Miniforge3# We deactive the `base` environment auto activationconda config --set auto_activate_base false# We unload current `base` environmentconda deactivate# (base) prefix in prompt must have disappeared
How to display the effective conda configuration?¶
For diagnostic purpose, the following command displays the full conda configuration.
conda config --show...