-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Docker stacks foundation image build fails with current mamba #2146
Comments
+1 here. |
I added the following to my build script to work around it. I'm hoping I don't also have to pin it. sed -i "s/latest/1.5.10/g" ./docker-stacks/docker-stacks-foundation/Dockerfile |
Mamba 2.0.0 has just been released. @jjerphan is the failure above
expected? |
It's a regression, we are working on a fix. |
It would be a good practice to pin micromamba version, regardless of the fix |
I pushed a fix preventing mamba 2.0.0 from installing.
Note: the error on our side occurs with Pinning micromamba version would not have helped here, as far as I understand: the error is caused by mamba, and the latest mamba would have still been installed, regardless of micromamba version. Pinning mamba version is also not something I would like to do - I prefer this repo to have unpinned versions for almost everything, and it works well - people eventually get the latest versions of software they use, and maintenance is much easier as well. |
You are correct. |
We have released micromamba 2.0.2 which should fix this issue, can you confirm it does? |
The There are still remaining issues with mamba v2, which prevent us from updating, please, take a look here: #2147 |
What docker image(s) are you using?
base-notebook, docker-stacks-foundation, minimal-notebook, pytorch-notebook, scipy-notebook
Host OS system
Ubuntu 22.04
Host architecture
x86_64
What Docker command are you running?
Docker build
How to Reproduce the problem?
Build docker stacks foundation image, the build throws an error
Command output
No response
Expected behavior
No response
Actual behavior
build results into the following error,
Anything else?
No response
Latest Docker version
The text was updated successfully, but these errors were encountered: