fix(ci): agent-base BASE_IMAGE + cache → harbor (zot 32B blob short-read) - #47
Merged
Conversation
…32B blob as 0 bytes) `Docker (agent base)` has been failing for a week with `short read: expected 32 bytes but got 0: unexpected EOF` at FROM-layer resolution. The 17d handoff hypothesized buildx state corruption / attestation manifest issues and ruled out a Ceph RGW small-blob bug because two previously-tested blobs (756B + 263B) served correctly from zot. Today's check on the actually-failing blob shows the bug: curl -I https://registry.blockcast.net/v2/paperclip/blobs/sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1 HTTP/2 200 / content-length: 0 ← truncated to zero curl -I --resolve harbor.blockcast.net:443:69.25.95.125 \ https://harbor.blockcast.net/v2/paperclip/paperclip/blobs/sha256:4f4fb700... HTTP/2 200 / content-length: 32 ← correct Same Phase A zero-byte-blob pattern, different blob. zot's Ceph RGW backend silently zero-truncates some small blobs on read. Harbor's filesystem-backed registry-v2 storage serves the same blob correctly. Fix: swap the agent build's BASE_IMAGE pull + buildcache to harbor. Phase B (BLO-5717, #213 onprem-k8s + #42-#45 paperclip) already parallel-pushes server images to both registries, so the sha-tag exists in harbor when this workflow runs. The buildcache moves fresh (no buildcache-v6 has been published yet — the build has been failing all session). This is also strategic alignment with Phase D zot retirement (~3-7 days out per the harbor cutover plan). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
6 tasks
1 task
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
Docker (agent base)has been failing for a week withshort read: expected 32 bytes but got 0: unexpected EOFat FROM-layer resolution. Root cause: zot's Ceph RGW backend silently truncates some small blobs to 0 bytes on read. Phase A (handoff 17d) ruled this out after checking the 756B + 263B buildcache blobs, but the actually-failing blob is the 32-byte FROM-layer descriptorsha256:4f4fb700...which IS truncated on zot.Evidence
HTTP/2 200/content-length: 0← BUGHTTP/2 200/content-length: 32✅Fix
BASE_IMAGEfrom\${{ vars.BLOCKCAST_REGISTRY_HOST }}/paperclip:...→harbor.blockcast.net/paperclip/paperclip:...cache-from/cache-toto harbor for the same reason (any small cache blob could trip the same Ceph RGW truncation)Phase B parallel-push (BLO-5717, onprem-k8s#213 + paperclip#42-#45) already publishes server images to both registries, so the sha tag exists in harbor when this workflow runs. No new infrastructure needed.
Buildcache moves fresh — no `buildcache-v6` has been published yet because the build has been failing all session, so there's no continuity loss.
This is also strategic alignment with Phase D zot retirement (~3-7 days from now).
Test plan
🤖 Generated with Claude Code