mamba: mamba install failure with current (fresh) anaconda install
- Installing on Debian 10 in a Linux container on a Chromebook, but this has failed on Ubuntu 18 also.
- install Anaconda using: Anaconda3-2022.05-Linux-x86_64.sh
- then
conda update -y --all - then check that
conda-forgeis the current channel (and there are no others) - then
conda install -c conda-forge mamba - wait interminably as conda fails to resolve dependencies, eventually saying
(base) chet@penguin:~$ conda install -c conda-forge mamba
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): /
done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: /
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
Examining bcrypt: 25%|██████████████████████████████████████████████▎ | 110/437 [07:07<1:04:57, 11.92s/- (base) chet@penguin:~$
Eventually it failed, but without an error-message.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 5
- Comments: 19 (1 by maintainers)
I really don’t recommend using the Anaconda distribution. It’s much better to start with
miniforgeormambaforge(comes pre-installed with mamba), orminiconda:I also had the same issue. I like starting with Anaconda as it has a large set of packages pre installed. Is there a similar way to start with mamba and a similar large list of packages?
Indeed not a pleasant thought, more about that in #1724 as @jonashaag pointed out. My understanding: once mamba is installed together with the last compatible conda (conda=4.12.0), the mamba requirements prevent an upgrade of conda (to conda=4.13) in that environment.