-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mamba clean crash #3044
Comments
Reported in #3033 (comment) . |
This is still happening to me inside Docker while building the container. Mamba version 1.5.4, conda 23.11.0 |
@rohit-guitar |
The mamba versions `1.5.3` and `1.5.4` have an issue that will fail the docker build, see mamba-org/mamba#3044. Pining the version to `1.5.2` until the problem is fixed upstream.
On all systems we have mamba 1.5.4, I have the same problem in our cli for linux and mac but
|
Workaroundinstead of |
yes this certainly works but the error is an upstream error for Linux systems. |
It fails also on Windows. Somehow it continues there which I assume is not correct. Crashes or Exceptions should behave similiar. |
I've released mamba 1.5.5 with the fix included. |
Will check it once we can update it via |
This works for us. Thx. |
@ThomasHezard maybe you can close this issue, if it's fixed for you. |
Fixed with the 1.5.5 release, many thanks 🙏 |
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
clean, crash
Latest version of Mamba
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
The command
mamba clean
ends with error for all the options I tried:mamba clean -a
mamba clean -i
mamba clean -p
mamba clean -t
mamba clean -l
The error is always the same:
No module named 'conda.cliconda'
followed by an error report (see below)
Problem is the same with or without an activated environement.
conda clean
works fine with all options.My
miniforge3
install is only a few days old, no plugins, I just created one simple env and and runmamba update conda mamba
once.mamba info / micromamba info
Logs
NB: I purposefully removed some sensitive env variables, but I'm almost 100% sure these have nothing to do with the issue here.
environment.yml
No response
~/.condarc
no .condarc for now
The text was updated successfully, but these errors were encountered: