Linux is where Micromamba feels most at home. This guide installs it on Ubuntu (the steps also work on Debian, Fedora and other glibc-based distributions), sets up activation and creates a first environment.
Requirements
- A glibc-based distribution such as Ubuntu, Debian, Fedora or CentOS. Alpine Linux is not supported natively.
- One of the supported architectures: x86-64, aarch64, ppc64le or riscv64.
curl, plustarwith bzip2 support for the manual method.- No root access: everything installs in your home folder.
Step 1: Prepare Ubuntu
sudo apt update
sudo apt install -y curl bzip2
Step 2: Run the official install script
"${SHELL}" <(curl -L micro.mamba.pm)
The script asks four questions:
- Binary folder, default
~/.local/bin. - Init shell, default yes. Accept it so
activateworks. - Configure conda-forge, default yes.
- Prefix location, default
~/micromamba.
The documentation uses "${SHELL}" <(curl ...) instead of piping into bash because piping does not work with these prompts. If you prefer to read the script first, download install.sh (it is included in the main.zip on our download section) and run it locally.
Step 3: Reload your shell
source ~/.bashrc
micromamba --version
If you see "command not found", make sure ~/.local/bin is on your PATH: add export PATH="$HOME/.local/bin:$PATH" to ~/.bashrc.
Step 4: Configure channels
If you skipped the conda-forge question, set it now. Using conda-forge alone avoids conflicts with Anaconda's default channels:
micromamba config append channels conda-forge
micromamba config set channel_priority strict
Step 5: Create your first environment
micromamba create -n first python=3.12 numpy
micromamba activate first
python -c "import numpy; print(numpy.__version__)"
Alternative: manual binary install
For servers where you do not want to run a script, extract the binary directly:
curl -Ls https://micro.mamba.pm/api/micromamba/linux-64/latest | tar -xvj bin/micromamba
./bin/micromamba shell init -s bash -r ~/micromamba
source ~/.bashrc
Use linux-aarch64 for ARM64 machines such as Raspberry Pi 4/5 with a 64-bit OS, or linux-ppc64le for POWER.
Installing a specific version
Set VERSION before running the script to pin a release. Release versions include a build number, for example 2.10.0-0:
VERSION=2.10.0-0 "${SHELL}" <(curl -L micro.mamba.pm)
Ubuntu on WSL
Under Windows Subsystem for Linux, follow the same Linux steps inside the Ubuntu terminal. Keep projects inside the Linux file system (for example ~/projects) for better performance.
Keeping it updated
micromamba self-update
Check the official changelog before upgrading production machines.
Fedora, Debian and other distributions
The same script works on any glibc-based distribution. Only the prerequisite command changes:
sudo dnf install -y curl bzip2 # Fedora, RHEL, Rocky
sudo apt install -y curl bzip2 # Debian, Ubuntu, Mint
sudo pacman -S --needed curl bzip2 # Arch, Manjaro
Using zsh or fish on Linux
The script detects the shell it was started from and initializes that one. If you switch shells later, initialize the new one yourself, for example micromamba shell init -s zsh -r ~/micromamba, then open a new terminal.
Troubleshooting the Linux install
| Problem | Fix |
|---|---|
| "Failed to detect your OS" | Your CPU architecture is not in the release list (for example 32-bit). Use a 64-bit system. |
tar: bzip2: Cannot exec | Install bzip2 with your package manager. |
| Binary will not run on Alpine | Alpine uses musl; use a glibc-based distribution or container. |
| Prompts do not appear | Use the documented "${SHELL}" <(curl ...) form instead of piping into bash. |
Next steps
Learn to create environments from files and see how activation works.