Reference the image by tag in the release smoke test - #13
Merged
Conversation
The smoke test resolved the image as IMAGE@digest and then passed --platform to docker run, which fails with "cannot overwrite digest" (exit 125): a digest pins a single manifest, so --platform cannot select a different one from the index. Reference the version tag instead, and pull each platform explicitly before running it so the correct architecture is present locally. Verified against the published keeper/gchat-app:v1.0.0-rc.1: both linux/amd64 and linux/arm64 report the expected architecture and exit with the expected configuration error.
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
The release smoke test referenced the image as
IMAGE@digestand passed--platformtodocker run, which fails withcannot overwrite digest(exit 125). A digest pins a single manifest, so--platformcannot then select a different one from the index.Reference the version tag instead, and pull each platform explicitly before running it.
Context
Hit on the
v1.0.0-rc.1run. Everything up to and including the push succeeded, sokeeper/gchat-app:v1.0.0-rc.1is published correctly:Both platforms were then verified by hand against that published image, reporting
x64/arm64on Node 22 and exiting with the expected configuration error. The corrected loop was run verbatim against the same image before committing.Because published version tags are immutable by design, the next release candidate is
v1.0.0-rc.2rather than a re-run ofrc.1.