PAR-329
0
Docker build-and-push fails: attestations (provenance/SBOM) unsupported on the default buildx docker driver
Pending ReleaseUrgentUnassignedTreasury APIBug
Treasury REST API · Build and Push Docker Image to Harbor fails at the build step on every develop push:
ERROR: failed to build: Attestation is not supported for the docker driver.
##[error]buildx failed with: Learn more at https://docs.docker.com/go/attestations/
Cause
.github/workflows/treasury-rest-api-docker.yml sets provenance: true + sbom: true on docker/build-push-action@v6 (added for audit finding global/infra/0004), but no docker/setup-buildx-action step runs first. Without it the action falls back to the default docker driver, which cannot emit attestations — only the docker-container driver can.
Impact
- No image has been pushed for the current
developSHA, so thedevelopment-sha-*tag Argo CD Image Updater watches is stale and UAT is not running the latest build. - The
develop→mainrelease PR (#2) shows this as its only red check (mergeStateStatus: UNSTABLE), and merging would fail theproduction-sha-*push the same way — i.e. the release would merge but never deploy.
Fix
Add docker/setup-buildx-action@v3 ahead of the build step so buildx runs on the docker-container driver, keeping provenance/sbom intact.
Acceptance
- Workflow completes green on a
developpush. development-sha-<short>+latestland inparadaux-public/treasury-rest-apiin Harbor, carrying provenance and SBOM attestations.
Resources
- PR#2 Last major release ParadauxIO/hibernia-economy
- commit1dfdb00 Set up Buildx so provenance/SBOM attestations can build (PAR-329)ParadauxIO/hibernia-economy
Comments
No comments yet.
Activity
- ParadauxIO linked a pull request — PR #2 open — Last major release
- ParadauxIO linked a pull request — PR #2 open — Last major release
- tesks changed status to Status → Pending Release
- ParadauxIO linked a commit — Commit 1dfdb00 — Set up Buildx so provenance/SBOM attestations can build (PAR-329)
- tesks created the issue