fix(deploy): strip the tag from the dev-image ref before the skopeo probe #233
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/coding-lab!233
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "lab/20260725-1726"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The deploy wait step (issue #230, ADR-0056) passed
container.defaultImage's pinned ref to skopeo verbatim. The pin deliberately keeps the tag beside the digest for readability —buildpack-deps:stable-scm@sha256:07554a82…— but skopeo'sdocker://transport rejects refs carrying both a tag and a digest, so every probe attempt failed on parse before reaching docker.io and the step spun until the 30-minute deadline killed the deploy.The pin itself is correct: podman on the host accepts the
name:tag@digestform and pulls by digest, and the tag-beside-digest convention comes from ADR-0053/0056. The fix lives in the probe alone — after the exactly-one extraction guard, the tag is stripped (sed -E 's/:[A-Za-z0-9._-]+@sha256:/@sha256:/', the same tag charset the extraction grep matches) and skopeo inspectsname@digest. The digest alone determines what resolves, so the probe proves the same pull.Verified locally: the extraction + strip pipeline against
nix/module.nixyieldsdocker://docker.io/library/buildpack-deps@sha256:07554a82…, andskopeo inspect --no-tagson that ref resolves anonymously (the tag+digest form reproduces the CI parse error).Closes #232
🤖 Generated with Claude Code