Add tag based multi arch docker build using GitHub Workflows #2229
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.
Hey,
I added a github workflow which should build multi-arch docker images for every new tag.
I also added the possibility to push the images to ghcr.io (GitHub Packages)
In addition to that, i added a build cache, becuase building images with qemu can quite take a while (around 20 min), so it should be much faster for subsequent builds.
The tagging behaviour should be identically to the current docker hub repo
When a new stable tag is published, e.g. v0.50.1, then the following tags will be created: 0.50.1, 0.50-latest, latest
When a new beta tag is published, e.g. v0.51.1-beta, then the following tags will be created: 0.51.1-beta, 0.51-latest
For the action to work, only the two secrets
DOCKER_USERNAME
&DOCKER_PASSWORD
need to be created and filled in the repo settings. For ghcr.io to work, no secrets are needed, but i think the package visibility needs to be changed after the first build/push.If this PR gets merged, one would possible need to update the release routine, as everything docker related is now done by GitHub.
You can see my test images here.
Would close #902