Docker Buildx v0.10.0 introduced a breaking change causing multi-architecture manifests to use oci instead of dockerimageType formats. The release notes warn about issues with registry and runtime support. This already caused a issue in this repo (see https://github.com/cypress-io/cypress-docker-images/issues/1141). It is unknown whether allowing the manifest imageType to change for Cypress Docker images would cause usage issues in users' environments and it would have to be considered as a breaking change for Cypress Docker.
This repo is currently using Buildx v0.9.1 so this issue needs to be considered and prepared before any update to Buildx v0.10.x takes place:
Merging this PR should have no impact on the current build workflow. It prepares for the update to Docker Buildx v0.10.0 and later, and it protects against changes to any published manifest's imageType.
Supports resolution of
Issue
Docker Buildx v0.10.0 introduced a breaking change causing multi-architecture manifests to use
oci
instead ofdocker
imageType
formats. The release notes warn about issues with registry and runtime support. This already caused a issue in this repo (see https://github.com/cypress-io/cypress-docker-images/issues/1141). It is unknown whether allowing the manifestimageType
to change for Cypress Docker images would cause usage issues in users' environments and it would have to be considered as a breaking change for Cypress Docker.This repo is currently using Buildx v0.9.1 so this issue needs to be considered and prepared before any update to Buildx
v0.10.x
takes place:16.17.1
Change
In order to keep the current manifest schema as follows:
instead of moving to
an environment variable setting BUILDX_NO_DEFAULT_ATTESTATIONS=1, introduced in Buildx 0.10.4, is added to the
push
job of the circle.yml workflow.