Mamba command not found (make mamba command available outside base environment) about mamba HOT 18 CLOSED

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

from mamba.

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

from mamba.

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

from mamba.

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"

from mamba.

from mamba.

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

from mamba.

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

from mamba.

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

from mamba.

this is fixed for linux now -- need to confirm that it works on osx & win as well (win not yet released).

from mamba.

fixed by putting a link to mamba in the condabin directory.

from mamba.

yep, should be fixed on windows, too.

What version do you have? Did you run conda init?

from mamba.

I am using the latest version. I did try conda init but still the same error.

from mamba.

can you post conda info and the contents of your base env condabin folder?

from mamba.

@wolfv I believe that does not work when one does not have write access to condabin, correct? I am on a shared cluster environment where the base environment and packages in general are managed centrally.
I tried

• updating mamba
• remove the env in which mamba was and reinstall
  But it still does not work.

from mamba.

for mambaforge on osx a simple mamba() { ~/mambaforge/bin/mamba "$@" ;} in .zshrc works too. tested on osx-arm64.

from mamba.

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

Where did you add this in bashrc? It says my base env is micromamba but I can't seem to run 'mamba' in the terminal anywhere. Strangely enough, all my packages and the environment is working fine and being recognized by VScode.

from mamba.

Please create a new ticket using the issue template and show exactly what you did and what you expected

from mamba.

This is still an issue. Installing with mambaforge-pypy first runs into the issue of missing DLLs. After manually copying the files to the correct location, mamba works in the miniforge base env, but is not found in an environment created with mamba create.

My workaround for now is this:

• create a folder somewhere and inside it a link to the mamba.bat from mambaforge-pypy3\condabin\mamba.bat
• add that folder to the path in the windows settings
• use mamba.lnk instead of mamba for all commands once the env is activated
• once that works, you can change the PATHEXT to include links, so you don't have to type .lnk

( cc @foobar41 maybe this helps you too )

The reason I made a new folder instead of adding condabin to the path is that I do not want the mamba's conda executables to clash with my existing conda installation.

from mamba.