Creates 3 Google Container Registry images instead of the one

[murphman300]

Troubleshooting

Before submitting a bug report please read the Troubleshooting doc.

Behaviour

On pretty out of the box setup, the action creates 3 GCR images, and applies a Created timestamp dating back to 1969.

Steps to reproduce this issue

The result on GCR was this:

Now the result is this:

Expected behaviour

The action deploys 1 image and tags that one as latest

Actual behaviour

The action deploys 3 images, instead of 1, the first one being uploaded being the right one

Configuration

This file has had no commits this week and was working up until 24h ago

      - name: Build docker image
        uses: docker/build-push-action@v3
        with:
          context: .
          file: ./apps/<project-name>/Dockerfile
          push: true
          tags: |
            gcr.io/${{ secrets.GCP_PROJECT_ID }}/<project-name>-ssr:${{ github.sha }}
            gcr.io/${{ secrets.GCP_PROJECT_ID }}/<project-name>-ssr:latest
          build-args: |
            some args here..
          cache-from: type=local,src=/tmp/.buildx-cache
          cache-to: type=local,dest=/tmp/.buildx-cache-new

Logs

Download the log file of your build and attach it to this issue.

Logs don't indicate anything job side - however, when i pull one of those images of 0 or ~1.4KB in size i get this error from docker:

unsupported media type application/vnd.in-toto+json

[tonistiigi]

docker/buildx#1533

[murphman300]

docker/buildx#1533

I'll try this out as, indeed, we didn't set that flag. Thanks @tonistiigi !

Kind of an interesting lapse of timing and communication from Cloud run if you ask me however.. lol

[murphman300]

Fixed indeed

[petr-nazarov-yoobic]

This issue also can cause the following error in gcp cloud run Image [name] not found. This is how I ended up here. As @tonistiigi mentioned, setting provenance: false fixes it. Note, this is only supported in docker/build-push-action@v3 not v2.