kevinveenbirkenbachandClaude Opus 5 3f973eb137 fix(images): resolve the base image per distro, not once for the default ...

Every distribution built FROM `base-debian`, so the arch, ubuntu, fedora and
centos images were all asking the registry for the debian parent.

push.sh exports INFINITO_DISTRO from MATRIX_DISTRO and then sources the env
layer, which is correct as far as it goes: load.sh snapshots caller-set values
and restores them, so the distro survives. INFINITO_PARENT_IMAGE is not set by
the caller, though, and arrives already materialised in .env, rendered for
whichever distro generated that file. Setting the distro in a loop therefore
never reaches the reference derived from it.

The new resolver renders it through utils.distros.base_image() rather than
composing the string, because test_distros_spot rejects an image reference
built anywhere but the SPOT. It sits beside local.sh, ci.sh and service_ref.sh,
which resolve the other image names the same way.

Verified: arch, fedora and ubuntu now resolve to three different parents where
they previously resolved to one. shellcheck is clean and test_distros_spot
passes, which is what proves the resolver stays inside the SPOT.

Not verified: the build step that calls it. push.sh runs only in CI, and the
base images are not published yet, so a real run still stops at the pull before
it reaches this line.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-21 10:26:26 +02:00

..

ci.sh

fix(ci-image): build node images locally under act instead of resolving ghcr

2026-07-29 23:23:55 +02:00

local.sh

style: delete every comment the comments-valid policy rejects

2026-08-18 03:22:02 +02:00

parent.sh

fix(images): resolve the base image per distro, not once for the default

2026-09-21 10:26:26 +02:00

service_ref.sh

…