Skip to content
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

COMP: Docker build suddenly stopped working, needs classic solver #673

Merged
merged 1 commit into from
Jun 10, 2024

Conversation

cookpa
Copy link
Member

@cookpa cookpa commented Jun 10, 2024

Something under the hood is causing the mamba solver to fail, reproduced on my Ubuntu machine as well as on the GHA runner. Using the classic solver appears to fix it

@gdevenyi
Copy link

This doesn't look the "best practice" for setting up a config:

conda config --add channels defaults
conda config --add channels conda-forge
conda config --set channel_priority strict

@gdevenyi
Copy link

Personally, I've had very good results switching to the micromamba docker and building up an environment using it:
https://micromamba-docker.readthedocs.io/

@coveralls
Copy link

Coverage Status

coverage: 84.688%. remained the same
when pulling 839496b on conda_classic_solver
into c4f0e32 on master.

@cookpa
Copy link
Member Author

cookpa commented Jun 10, 2024

Merging for now because it's working again, a rewrite for micromamba would be a good idea later

@cookpa cookpa merged commit b3056d5 into master Jun 10, 2024
3 checks passed
@cookpa cookpa deleted the conda_classic_solver branch June 10, 2024 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants