fix(ci): repin the toolchain image — 32747a0 vanished from the registry #771

Closed
timothy wants to merge 1 commits from fix/ci-image-repin into main
1 Commits
Author SHA1 Message Date
timothy e7b3675a6b fix(ci): repin the toolchain image — 32747a0 vanished from the registry
review-verdict/h10 Awaiting review verdict for e7b3675
Review verdict / Set review-verdict status (pull_request_target) Successful in 14s
PR Gates / Docs update reminder (pull_request) Successful in 12s
PR Gates / decisions lifecycle (pull_request) Successful in 20s
PR Gates / Script tests (pytest) (pull_request) Successful in 2m16s
PR Gates / CI image pin matches docker/ci (pull_request) Failing after 6s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 9m21s
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Canceled after 0s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Canceled after 0s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Canceled after 0s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Canceled after 0s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Canceled after 45s
Every `container:` job in docker-build.yml (`test`, `migrations`, `functional-e2e`,
`api-docs`, `format`) has been failing after 1-2s with:

  Error response from daemon: failed to resolve reference
  "192.168.1.95:3000/timothy/ersatztv-ci:32747a0": not found

That is repo-wide and blocks BOTH required contexts, so nothing could merge. It is not a
code defect: the pin is unchanged on main, and the image simply is not in the registry any
more. `GET /v2/timothy/ersatztv-ci/tags/list` returned 3a6174c, 40dc752, 7280a91, 9881d1f,
9928be8, 9dc360c, buildcache, latest — no 32747a0.

Last known good: run 1933 (push to main f9f8f65c, 2026-08-11T19:26Z) started its container
jobs successfully. First observed failure: run 1937, 2026-08-13T17:19Z. So the tag was
removed from the registry somewhere in that ~2-day window; by what is not established, and
that is the open question, tracked separately.

`scan` (ersatztv#767) was green throughout, which is how the shape was identified quickly —
it is the one job with no `container:`, so it was the only one that could still start.

The fix is the documented two-step: `ci-image.yml` was dispatched on main, which republished
the toolchain as `:f9f8f65` (it tags by build-commit sha, so a rebuild yields a NEW tag rather
than restoring the old one), and this PR moves all six pin sites onto it. This PR's own green
run is the proof the new image works — that is exactly what the two-step exists for.

NOT done here: nothing has been changed to prevent a recurrence. A pin whose image can
disappear is a standing fail-open — CI goes red repo-wide and the only signal is a container
pull error buried in each job. Tracked separately rather than bundled into a restore.

Refs: #767
2026-08-13 19:26:39 +02:00