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

Unset the jobs variable from the opam config (faulty opam 2.0 behaviour) #92

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kit-ty-kate
Copy link
Contributor

opam 2.0 by default stores the number of cores of the current machine. While not too much of a big deal for users, this is extremely bad for the base images where the number stored will be around 72 but these can be used on any other machines.

This might help fighting the IO overload on the cluster.

@dra27
Copy link
Collaborator

dra27 commented Sep 8, 2022

The problem doing this in the base is that it breaks 2.0 - opam 2.1 recomputes the jobs variable if it's missing, but opam 2.0 just assumes "1". I think this wants to be in workflows as part of the root upgrade step?

@benmandrew
Copy link
Contributor

@kit-ty-kate can this be merged now that the opam PR is merged?

@kit-ty-kate
Copy link
Contributor Author

@benmandrew the opam PR only fixes things when upgrading to opam 2.2. David’s comment above is still very much the main blocker, so until the images are upgraded to a more recent opam by default this PR can’t be merged.

@kit-ty-kate kit-ty-kate marked this pull request as draft January 23, 2024 13:09
@shonfeder
Copy link
Contributor

iiuc, addressing ocurrent/docker-base-images#132 would unblock this.

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.

5 participants