Digest output is image ID, not RepoDigest

Troubleshooting

The output called digest is not in fact the digest that can be used to pull the image that was pushed to the repository. The metadata output has the same ID listed as "containerimage.digest".

Behaviour

Steps to reproduce this issue

1. Use docker/build-push-action@v2 to build and push any image
2. View the outputs of the step

Expected behaviour

Tell us what should happen

The output named digest should contain the digest of the image, not the ID.

i.e. the output of docker inspect $IMAGE | jq .[].RepoDigests

Actual behaviour

Tell us what happens instead

The output named digest contains the Image ID, i.e. the output of docker inspect $IMAGE | jq .[].ID

Configuration

• Repository URL (if public): https://hub.docker.com/layers/163513701/sajari/docd/1.2.0/images/sha256-abe87bda82fdf472763c5782bd787154fd5196dbf37bb5b94b3c757df71f0de3?context=repo

DockerHub reports the Digest to be: sha256:abe87bda82fdf472763c5782bd787154fd5196dbf37bb5b94b3c757df71f0de3

• Build URL (if public): https://github.com/sajari/docconv/runs/3377464865?check_suite_focus=true

docker/build-push-action@v2 outputs a digest of sha256:e72b6e4b4ed5763c94bfde0320282c8a3125152d8f2325d015c37a01eed2a9b2

• Workflow definition: https://github.com/sajari/docconv/actions/runs/1148980570/workflow

Logs

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

1_Publish Docker image.txt

[kpcyrd]

The official docker-publish.yml template still links to here:

      # Workaround: https://github.com/docker/build-push-action/issues/461
      - name: Setup Docker buildx
        uses: docker/setup-buildx-action@79abd3f86f79a9d68a23c75a09a9a85889262adf

Since this github issue is closed, can this workaround be removed?

[crazy-max]

Having dug deeper on this issue, the digest output contains the remote digest if you run docker/setup-buildx-action before building.

If you do not call setup-buildx, then it seems to incorrectly populate digest with the local image ID as reported in the OP.

Thanks for your feedback, will take a look and come back to you.