Build through artifactapi and get the internal CA into buildkit #2
Reference in New Issue
Block a user
Delete Branch "container-scaffold"
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 CI matrix overrode
BASE_IMAGEwithdocker.io/almalinux:9, so every CIbuild pulled the base straight from Docker Hub — uncached and rate-limited —
and the artifactapi path set in
distros/alma9/distro.envonly ever applied tolocal
make build.Pointing CI at artifactapi exposed a second defect: the
buildkit_configblockis dead YAML. The
plugin-docker-buildxbuild we run has noPLUGIN_BUILDKIT_CONFIG, sodocker buildx createran without--configandthe spawned buildkit container had no internal CA. The plugin generates that
config itself, but only when
registryis set — which is why the tag buildpushed fine and a PR build could not have pulled.
BASE_IMAGEat the artifactapi dockerhub remoteregistryon every step and drop the deadbuildkit_configblocksci/check-distros.shwhen a matrix value restating adistro.envkey drifts from it