docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

build(cloud): call out conflict with default provenance in gha 

`build-push-action` and `bake-action` add default provenance
attestatiosn to images in versions 4.0.0 and later. This creates a
conflict with the default cloud pull in Docker Build Cloud.

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson 2024-03-11 17:44:20 +01:00
parent d6de5de66c
commit e6e8a96d4a
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
content/build/cloud/ci.md
View File

@ -33,6 +33,24 @@ See [Loading build results](./usage/#loading-build-results) for details.
{{< tabs >}} {{< tabs >}}
{{< tab name="GitHub Actions" >}} {{< tab name="GitHub Actions" >}}
> **Note**
>
> Version 4.0.0 and later of `docker/build-push-action` and
> `docker/bake-action` builds images with [provenance attestations by
> default](../ci/github-actions/attestations.md#default-provenance). Docker
> Build Cloud automatically attempts to load images to the local image store if
> you don't explicitly push them to a registry.
>
> This results in a conflicting scenario where if you build a tagged image
> without pushing it to a registry, Docker Build Cloud attempts to load images
> containing attestations. But the local image store on the GitHub runner
> doesn't support attestations, and the image load fails as a result.
>
> If you want to load images built with `docker/build-push-action` together
> with Docker Build Cloud, you must disable provenance attestations by setting
> `provenance: false` in the GitHub Action inputs (or in `docker-bake.hcl` if
> you use Bake).
```yaml ```yaml
name: ci name: ci