Rolls the initial base image back to Jammy to avoid issues with MPICH #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
slabasan
reviewed
Jul 8, 2025
Collaborator
There was a problem hiding this comment.
I'm going to merge this as is, but I think we should update the name of this file to be more descriptive than old. Are these the requirements with noble?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
There is an extremely annoying issue with MPICH on Ubuntu Noble (documented here) that makes
libmpich.sotry to use PMIx for bootstrapping. However, both MPICH'smpiexecand Flux'sflux rundo not support PMIx out of the box. As a result, trying to run any MPI application will result in each process being stuck in their own communicator.To fix this issue, this PR rolls back the version of Ubuntu from Noble (24.04) to Jammy (22.04).