mamba: Mamba command not found (make mamba command available outside base environment)

I installed minimamba and create a minimal voila environment. The issue is that from the base environment I have the mamba command available, but whenever I activate the voila environment mamba is not available anymore…

mamba_trace

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 2
  • Comments: 18 (6 by maintainers)

Commits related to this issue

Most upvoted comments

For anyone on macOS using Catalina or newer and thus have zsh instead of bash conda init zsh

yep, indeed we need to figure out how to make the mamba command available outside the base environment! Thanks for reporting.

As a workaround adding mamba() { ~/.conda/envs/base_mamba/bin/mamba "$@" ;}to ~/.bashrc does the trick though

This seems tricky because ideally we would want mamba to be in the user’s PATH even when there is no active conda environment (post conda deactivate) as well so that mamba env create ... work regardless of which if any conda env is active. In our build process I’m just linking mamba to a bin dir which seems to work well:

ls -s "$(conda info --base)/bin/mamba" "/usr/local/bin/mamba"

I still cannot run mamba in another environment, runs only in base. Can anyone help ? Should I add to path environments or something ?

sorry for the late reply. It is working now, after reinstall.

is this fixed for Windows? I am still getting this error.

Actually there is another directory in the conda base environment called ‘condabin‘ which is where conda itself is adding a copy of the conda executable to be available in all environments. I was planning to do the same, but from the recipes build.sh

However, this would not work completely outside of conda.

On Tue 9 Jul 2019 at 10:36, Xiao Yu notifications@github.com wrote:

This seems tricky because ideally we would want mamba to be in the user’s PATH even when there is no active conda environment (post conda deactivate) as well so that mamba env create … work regardless of which if any conda env is active. In our build process I’m just linking mamba to a bin dir which seems to work well:

ls -s “$(conda info --base)/bin/mamba” “/usr/local/bin/mamba”

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/QuantStack/mamba/issues/34?email_source=notifications&email_token=AAGYCPU4JDYIPEZMT4IVBVTP6SPANA5CNFSM4HW3ZQ7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZQO6PI#issuecomment-509669181, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGYCPSTDGP6ZSSAZ2ZTT3LP6SPANANCNFSM4HW3ZQ7A .