Automatically publish new Docker images #291
Draft
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
linuxgemini
added a commit
to linuxgemini/acme-dns
that referenced
this pull request
Feb 9, 2022
On-behalf-of: Johannes Doll <jodoll@users.noreply.github.com> Signed-off-by: İlteriş Yağıztegin Eroğlu <me@linuxgemini.space>
linuxgemini
added a commit
to linuxgemini/acme-dns
that referenced
this pull request
Feb 9, 2022
Co-authored-by: Matthias Schneider <ms@wck.biz> Co-authored-by: Johannes Doll <jodoll@users.noreply.github.com> Signed-off-by: İlteriş Yağıztegin Eroğlu <me@linuxgemini.space>
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.
This PR adds a GitHub workflow to automatically build and publish new Docker images on several.
It is for the most part an adapted version of the official
Publish Docker Containerworkflow.Why?
Regular rebuilds of this image are needed to mitigate vulnerabilities in the used base image, even when no changes are made.
In Addition, the latest revision of
masterwill always be accessible via Docker image, when including this workflow.When are images published?
masterandlatestare updatedv: New tag with with that name is publishednightlyis updatedPublishing
Images are currently published to ghcr.io and will occur as published artifact on this repositories GitHub page. The images can be retrieved by referencing
ghcr.ioas registry (e.g.docker pull ghcr.io/jodoll/acme-dns:docker_publish).Nevertheless, it may be desirable to also (or exclusively) release the images on Docker Hub. I'd be glad to incorporate this into this PR, but I'll need to know how to reference some secret to enable this workflow to access Docker Hub.
Just let me know if this desired and I'll research and make a proposal on how to do this.
Draft
Any feedback is welcome and I'll remove the draft state once the publishing issue is sorted out.