fix(devcontainer): publish only multi-arch tags, push per-arch by digest#384
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix devcontainer tagging to align with latest digest
fix(devcontainer): publish only multi-arch tags, push per-arch by digest
Jun 2, 2026
Owner
|
@copilot resolve the merge conflicts in this pull request |
…ner-align-tagging # Conflicts: # .github/workflows/devcontainer-prebuild.yaml
Contributor
Author
Merged |
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
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.
The
dotfiles-devcontainerpackage exposed rolling:amd64/:arm64tags that drifted out of sync with the platform digests inside:latest(the:amd64tag pointed at a newer digest than:latest's amd64 entry). Each native-runner build pushed its own per-arch tag independently, and the merge job composed:latestby resolving those mutable tags.Workflow (
.github/workflows/devcontainer-prebuild.yaml):amd64/:arm64tags; per-arch images are stored untagged.:latestand:vX.Y.Zfrom the exact digests built in the same run viadocker buildx imagetools create, so the multi-arch tags always reference matching platform images.devcontainers/ciaction with a directdevcontainer buildcall (the action always tags, which is what created the stray tags).:latest(same pattern asci.yaml) plus the CLI's inline cache. PR runs build for validation only.Tests (
tests/bash/validate-devcontainer.bats)imagetools createcommand.imageTag: ${{ matrix.arch }}rolling tags.Notes
exporting manifest listoutput: the Dev Container CLI doesn't forward buildx's--metadata-file, so this is the available capture path.:latest@sha256:…pin indevcontainer.jsonstill resolves —:latestremains a multi-arch manifest list.