Work around broken Docker image by Rocky Linux (until CentOS 7 is EOL) #114
Conversation
This file contains 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
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.
As pointed out by @job,
docker.io/rockylinux/rockylinux:9doesn't shipyumcurrently. After talking to Rocky Linux folks, it seems to be accidentially caused when updating the docker image to Rocky Linux 9.4 after switching from imagefactory to kiwi as image builder. Given we still support CentOS 7 (which reaches EOL at 2024-06-30), I added a not so nice workaround for the next two months. After EOL of CentOS 7, I will suggest to switch fromyumtodnf, becauseyumis anyway just a wrapper todnfsince RHEL/CentOS/Rocky Linux 8 (and in Fedora even longer).