You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using micromamba to install from an environment file, non-zero exit codes from the pip install step don't result in a non-zero exit code from micromamba. This means that docker builds etc. using micromamba can "succeed" even without pip dependencies installed successfully, resulting in silently broken images.
pip failed, but the micromamba process still raises a zero exit code. In the same docker image, directly running pip install nonexistentpythonpackage==123.123 prints the same error but exits with code 1.
I think this may be related tangentially to #1100 which was solving the problem of pip getting OOM killed?
The text was updated successfully, but these errors were encountered:
When using micromamba to install from an environment file, non-zero exit codes from the
pip install
step don't result in a non-zero exit code frommicromamba
. This means that docker builds etc. using micromamba can "succeed" even without pip dependencies installed successfully, resulting in silently broken images.Example: Using this simple
environment.yml
:and the
mambaorg/micromamba:0.20.0
docker image, the following output occurs:pip
failed, but themicromamba
process still raises a zero exit code. In the same docker image, directly runningpip install nonexistentpythonpackage==123.123
prints the same error but exits with code 1.I think this may be related tangentially to #1100 which was solving the problem of pip getting OOM killed?
The text was updated successfully, but these errors were encountered: