Repository navigation
Description
Assert, in pgCK's own release and before attestation, that every published arch shares one source commit and one measured glibc floor. Mirrors the gate oci-germination added at v0.7.31 — but at our layer, because theirs structurally cannot see us any more.
Why this cannot be delegated downstream
oci-germination's parity gate reads the max floor across every .so in /usr/lib/postgresql/18/lib/:
floor="$(cat /tmp/lib-$arch/*.so | strings | grep -o 'GLIBC_[0-9][0-9.]*' | sort -V | tail -1)"then compares that single number across arches. It caught pgRDF's v0.7.30 divergence only because pgrdf.so was the max on one side (amd64 2.34 vs arm64 2.39).
With pgrdf.so now measured at GLIBC_2.39 on both arches, a pgCK per-arch split up to 2.39 leaves the max at 2.39 on both sides — the gate passes and the divergence is invisible. Once pgCK also floors near 2.39 (#13), pgCK becomes fully invisible to that gate in both directions. The failure would then present as a runtime FATAL: could not load library on a lower-glibc base, with a green supply chain behind it.
So: the only place a pgCK arch split can be caught is pgCK's own release.
Scope
Pre-attest gate asserting, across {amd64, arm64} for each variant:
org.opencontainers.image.revisionis present, equal to the building commit, and equal across arches;- the measured floor (from the shipped
.so, not the annotation) is equal across arches; - the measured floor equals what
MANIFEST.jsonand the annotation claim — so a stamped lie fails the build rather than shipping inside a signature.
That last check is the one oci-germination cannot perform for us and pgRDF does not perform for itself.
Done when
- A deliberately divergent build (e.g. one arch built outside the pinned container) fails the gate and never reaches
attest-build-provenance. - The gate prints both arches' measured floors in the run log, so the number that ends up in
MANIFEST.jsonis auditable from CI output alone.
Relates
- ck-allinone: rebuild on pg18 + glibc>=2.38 base (adopt pgRDF v0.6.20 / pgCK pg18) sporaxis-com/oci-germination#20 / their v0.7.31 gate · 0.6.21: build both arches in a pg18/trixie container (same commit), truthful provenance base, arm64 boot gate + stamp base/commit pgRDF#67
- Depends on Unified trixie/pg18 release build — one pinned container, both arches, one commit (pgRDF#67 req 1) #13 (one build container) and Layer-only bundle form — single-tarball artifact + measured MANIFEST.json + multi-arch index (pgRDF#67 req 2/4, sporaxis#8) #15 (annotations + MANIFEST to check against).
Activity