Use versioned tags to identify Fedora version we use #57
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
|
After we merge this, we can prepare a switch to Fedora 35. I can also test it in my fork first to verify the zero impact on the older container images. |
hroncok
approved these changes
Jun 6, 2022
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.
With this change, all container images we push to the Docker hub will have two tags:
:archand:arch-fXX. Also, there is a new manifest for all:arch-fXXcontainer images:fXX. In that way, when we soon switch to Fedora 35, container images:arch-f34and the manifest:f34should stay untouched possibly to use for users who need older Pythons.I've run the action in my fork so you can already see the results in: https://hub.docker.com/repository/docker/fedorapython/fedora-python-tox/tags?page=1&ordering=last_updated