Open xfoxfu opened 1 year ago
Will disabling provenance solve the issue?
- uses: docker/build-push-action@v4
with:
provenance: false
...
No, because images are multi-arch.
No, because images are multi-arch.
May create a PR for this issue? I may not particularly understand how to solve this.
As this is not supported, the only way is to disable retention currently.
Currently the workflow is configured to preserve 5 untagged or
COMMIT_SHA1
container images. However, this is not suitable as GZCTF is currently publishing multi-arch + provenance-enabled containers. These containers will have tags applied on a virtual image, which contains metadata of actual images. The actual images is not tagged. Therefore, the images of previous versions is removed.Workaround: disable image retention.
Reference: