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…

About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 18 (6 by maintainers)
For anyone on macOS using Catalina or newer and thus have
zshinstead ofbashconda init zshyep, indeed we need to figure out how to make the
mambacommand available outside the base environment! Thanks for reporting.As a workaround adding
mamba() { ~/.conda/envs/base_mamba/bin/mamba "$@" ;}to~/.bashrcdoes the trick thoughThis seems tricky because ideally we would want
mambato be in the user’s PATH even when there is no active conda environment (postconda deactivate) as well so thatmamba env create ...work regardless of which if any conda env is active. In our build process I’m just linkingmambato a bin dir which seems to work well: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: