feat: publish container image to Docker Hub for discoverability#102
Merged
Conversation
Add Docker Hub as a second push target in the release workflow. GHCR remains the primary registry for all docs, Helm defaults, and install manifests (no rate limits on public packages). Changes: - Add Docker Hub login and image tags to release workflow - Sign Docker Hub image with cosign (same keyless flow) - Add dockerhub-readme job to sync docker/README.md on release - Create docker/README.md with Docker Hub-specific content - Add Docker Hub pulls badge to README.md - Add Docker Hub availability note to installation docs - Document Docker Hub in the release process Requires DOCKERHUB_USERNAME and DOCKERHUB_TOKEN secrets to be configured before the next release. Closes #12 Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
github-actions
Bot
added
area/ci
Docker Hub rate-limits and blocks automated link checks, causing false 404s in CI. The Docker Hub repo URL is validated by pull tests after each release instead. Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds Docker Hub as a second push target in the release workflow for discoverability. GHCR remains the primary registry for all documentation, Helm chart defaults, and install manifests.
Changes
.github/workflows/release.yamldocker/README.mdREADME.mddocs/getting-started/installation.mddocs/contributing/releasing.mdWhat stays the same
image.repositorystaysghcr.io/attune-io/attuneconfig/manager/kustomization.yamlstays GHCRdist/install.yamlstays GHCRPrerequisites before next release
Two repo secrets must be configured:
DOCKERHUB_USERNAME: Docker Hub username or bot account forattuneioorgDOCKERHUB_TOKEN: Docker Hub access token (read/write scope)Verification
After the first tagged release with this workflow:
docker pull attuneio/attune:vX.Y.Zworkscosign verifypasses for both GHCR and Docker Hubdocker/README.mdCloses #12