[PR #291] Automatically publish new Docker images #374

New issue

Open

opened 2026-03-13 16:20:25 +03:00 by kerem · 0 comments

kerem commented

2026-03-13 16:20:25 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/acme-dns/acme-dns/pull/291
Author: @jodoll
Created: 2/1/2022
Status: 🔄 Open

Base: master ← Head: docker_publish

📝 Commits (9)

46f1ba2 Add action to publish Docker image
4333f99 Enable docker publish action on feature branch
d26cb64 Rename docker publish workflow
00631eb Use fixed versions for actions in docker publish
933d70c Use @main version of cosign-installer
c42290f Switch to cosign-release 1.5.1
25549b3 Define tags in metadata-action
f690387 Publish all tags starting with v as release
30dfcf7 Run docker publish workflow only on master

📊 Changes

1 file changed (+99 additions, -0 deletions)

View changed files

➕ .github/workflows/docker-publish.yml (+99 -0)

📄 Description

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 Container workflow.

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 master will always be accessible via Docker image, when including this workflow.

When are images published?

Push to master: Tag master and latest are updated
New tag starting with v: New tag with with that name is published
Nightly: The tag nightly is updated

Publishing

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.io as 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.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/acme-dns/acme-dns/pull/291 **Author:** [@jodoll](https://github.com/jodoll) **Created:** 2/1/2022 **Status:** 🔄 Open **Base:** `master` ← **Head:** `docker_publish` --- ### 📝 Commits (9) - [`46f1ba2`](https://github.com/acme-dns/acme-dns/commit/46f1ba2f8b86bf1a6cd60202039eec5b02b1bf18) Add action to publish Docker image - [`4333f99`](https://github.com/acme-dns/acme-dns/commit/4333f9995897aab1628e88266822503d0c5fd3de) Enable docker publish action on feature branch - [`d26cb64`](https://github.com/acme-dns/acme-dns/commit/d26cb64449ae659b0610d7ea259b654839067d53) Rename docker publish workflow - [`00631eb`](https://github.com/acme-dns/acme-dns/commit/00631eb9d40ab171c8b319ffee49aab1034e99cf) Use fixed versions for actions in docker publish - [`933d70c`](https://github.com/acme-dns/acme-dns/commit/933d70cc0d3aeb5ad311d1f5b9673fab73258e45) Use @main version of cosign-installer - [`c42290f`](https://github.com/acme-dns/acme-dns/commit/c42290f2b284c07394fdef8b09f3704d83650415) Switch to cosign-release 1.5.1 - [`25549b3`](https://github.com/acme-dns/acme-dns/commit/25549b30a1f8f6c8f0f93a03c101d5ef04198b5f) Define tags in metadata-action - [`f690387`](https://github.com/acme-dns/acme-dns/commit/f6903876121025eb5b58ffd45143a62d34a1ab46) Publish all tags starting with v as release - [`30dfcf7`](https://github.com/acme-dns/acme-dns/commit/30dfcf73e3139f196ef329cf510883f7bc492925) Run docker publish workflow only on master ### 📊 Changes **1 file changed** (+99 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/docker-publish.yml` (+99 -0) </details> ### 📄 Description 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 Container` workflow. ## 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 `master` will always be accessible via Docker image, when including this workflow. ## When are images published? * Push to master: Tag `master` and `latest` are updated * New tag starting with `v`: New tag with with that name is published * Nightly: The tag `nightly` is updated ## Publishing Images are currently published to [ghcr.io](https://ghcr.io) and will occur as published artifact on this repositories GitHub page. The images can be retrieved by referencing `ghcr.io` as 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>