Use container images based on software layer's build node images #233
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
casparvl
approved these changes
Jan 28, 2026
Contributor
There was a problem hiding this comment.
I'm not the best person to review this, as I don't e.g. exactly know which packages would be needed in this container for it to do what it needs to do. But since this adds new containers, it can't break existing ones - and since I don't see anything strange purely from the syntax, I'm happy to merge it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds new container images that are based on the ones that we used for the software layer, and install some additional tools on top (e.g. Ansible). This allows us to also use
eessi_container.sh, and make it easier to update compat layers by using fuse mounts and overlays.For now I've left the old dockerfiles and the old CI workflow in place until we've tested this a bit more.