Open vizeit opened 3 days ago
+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 sed -i "s/'mamba' /'mamba==1.5.10' /g" ./docker-stacks/docker-stacks-foundation/Dockerfile
Mamba 2.0.0 has just been released. @jjerphan is the failure above
mamba list --full-name python
The following argument was not expected: --full-name
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
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