Repository navigation
chore(compose): repin to the multi-arch v1.3.0 index digest - #31
Merged
Merged
Conversation
The compose file still pinned the v1.2.0 digest, which is an amd64-only image. Re-pinned to the v1.3.0 OCI index digest so the pin resolves to the correct per-host image on both amd64 and arm64. Also updates the README's duplicate compose snippet, which would otherwise have drifted from the shipped file. Verified: sha256:03645909... is the live docker-content-digest of GHCR v1.3.0, and that index lists linux/amd64 and linux/arm64. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Re-pins the shipped
docker-compose.ymlto the v1.3.0 OCI index digest.The file still pinned the v1.2.0 digest, which is an amd64-only image — so the default deployment path would have kept users on the single-arch image even after multi-arch shipped.
This is the index digest, so Docker resolves it to the correct amd64 or arm64 image per host.
The README carries a duplicate of this compose block; it is updated too, so the two cannot drift.
Verification
sha256:03645909a810201b2a4297834969ead6118f3f9cad99fede1f5f2ac4947c4244is the livedocker-content-digestof GHCRv1.3.0linux/amd64andlinux/arm64docker compose configparses; no stale v1.2.0 digest remains anywhere in the repoNote
This changes what a user gets from
docker compose up: it moves them from v1.2.0 to v1.3.0. That is the intent — v1.2.0 predates multi-arch — but it is a behaviour change for anyone who pinned the file deliberately.