Repository navigation
Ignore attestation manifests when reading Docker Hub tags - #311
Merged
Merged
Conversation
The agents run 9c27cff, whose trixie docker-cli sends `docker build` through buildx, and buildx attaches a provenance attestation to every image by default. Docker Hub lists the attestation as an image with architecture "unknown", and `Bob.DockerHub.parse/1` returned it as an arch. Every per-arch image pushed since 2026-10-02 carries one. `Bob.Job.DockerManifest.publish?/4` then read a published manifest of `amd64, unknown` as spanning an arch its sources lack and left it alone. When one arch's build finished first, its manifest job published a single-arch manifest, and the job queued by the second arch never added it. 527 manifests in hexpm/erlang and hexpm/elixir, built on 2026-10-02 and 2026-10-06, are stuck with one arch; hexpm/elixir:1.20.4-erlang-28.5.0.7-debian-trixie-20261005, for example, has no arm64 image. `Bob.Job.DockerChecker.manifest/0` finds the same 527 mismatches every 15 minutes and queues 527 DockerManifest jobs, each making three Docker Hub requests and changing nothing. `parse/1` now drops entries with architecture "unknown", so the next DockerChecker run after deploy rebuilds those 527 manifests with both arches.
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.
The agents run 9c27cff, whose trixie docker-cli sends
docker buildthrough buildx, and buildx attaches a provenance attestation to every image by default. Docker Hub lists the attestation as an image with architecture "unknown", andBob.DockerHub.parse/1returned it as an arch. Every per-arch image pushed since 2026-10-02 carries one.Bob.Job.DockerManifest.publish?/4then read a published manifest ofamd64, unknownas spanning an arch its sources lack and left it alone. When one arch's build finished first, its manifest job published a single-arch manifest, and the job queued by the second arch never added it. 527 manifests in hexpm/erlang and hexpm/elixir, built on 2026-10-02 and 2026-10-06, are stuck with one arch; hexpm/elixir:1.20.4-erlang-28.5.0.7-debian-trixie-20261005, for example, has no arm64 image.Bob.Job.DockerChecker.manifest/0finds the same 527 mismatches every 15 minutes and queues 527 DockerManifest jobs, each making three Docker Hub requests and changing nothing.parse/1now drops entries with architecture "unknown", so the next DockerChecker run after deploy rebuilds those 527 manifests with both arches.