-
-
Notifications
You must be signed in to change notification settings - Fork 19.4k
CI: Pin conda in docker build #48139
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
Conversation
mroeschke
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this eventually affect other builds?
|
Not sure. We are using micromamba for most builds, so should not. I'll open a pr in parallel to check if we can switch to mambaforge as base image here. This should solve this. |
Sounds good. Switching to micromamba would probably be a preferred fix here. |
|
Yep agreed. This is only a temporary solution to get the ci passing agai anyway |
|
#48143 uses mambaforge as base image. Gets the ci back to green too |
is that the preference? and close this one? |
Yes, that would be my preference. |
|
Yep, let’s merge the other pr |
This gets ci green for now, but have to investigate what is wrong here. The first failing build updated conda from 4.13 to 4.14 with the
conda install mambacommand, hence the pin therecc @mroeschke