build: Disable SLSA Provenance metadata for our images #144
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Provenance metadata was newly enabled by default in buildx 0.10.0¹ and entails switching from older, Docker image manifest lists (application/vnd.docker.distribution.manifest.list.v2+json) to the newer, but roughly equivalent-in-concept, OCI image indexes (application/vnd.oci.image.index.v1+json).²
This switch happened automatically for us between these two builds:
due to an upgrade of buildx from 0.9.1 → 0.10.0 on the GitHub Actions runners we use for CI.
Unfortunately, Singularity doesn't support OCI image indexes (i.e. multi-platform images) until 3.6.0.³ While we'll likely need to require a newer Singularity version at some point anyway⁴, disabling the provenance metadata for now should restore compatibility with Singularity back to its 2.6 series. We don't need the provenance anyhow.
¹ https://github.com/docker/buildx/releases/tag/v0.10.0
² Provenance metadata is attached as additional entries in the image
index alongside the normal entries for each platform image.
³ nextstrain/cli#267
⁴ nextstrain/cli#274
Resolves nextstrain/cli#267.
Testing