Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Incorrect value for 'digest' output (same as 'imageid' for some reason)

See original GitHub issue

Troubleshooting

Before submitting a bug report please read the Troubleshooting doc.

Behaviour

Steps to reproduce this issue

Use the action to build and push a docker image
Inspect the value of the “outputs” shown in the console output in github actions

Expected behaviour

ImageID should be the ID of the docker image Digest should be the digest of manifest

Actual behaviour

Digest is the same as the ImageID

Configuration

Repository URL (if public):
Build URL (if public):

# paste your YAML workflow file here and remove sensitive data

Logs

2022-03-26T14:37:51.9712149Z #13 DONE 4.4s
2022-03-26T14:37:51.9828664Z ##[group]ImageID
2022-03-26T14:37:51.9829520Z sha256:911746252f615a3a30e37f10d8f34824a441210b82ce7cb01404752879db6f14
2022-03-26T14:37:51.9876893Z ##[endgroup]
2022-03-26T14:37:51.9877499Z ##[group]Digest
2022-03-26T14:37:51.9878026Z sha256:911746252f615a3a30e37f10d8f34824a441210b82ce7cb01404752879db6f14
2022-03-26T14:37:51.9879226Z ##[endgroup]
2022-03-26T14:37:51.9879802Z ##[group]Metadata
2022-03-26T14:37:51.9880101Z {
2022-03-26T14:37:51.9880535Z   "containerimage.digest": "sha256:911746252f615a3a30e37f10d8f34824a441210b82ce7cb01404752879db6f14"
2022-03-26T14:37:51.9880942Z }

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:8 (2 by maintainers)

Top GitHub Comments

2reactions

crazy-maxcommented, Apr 5, 2022

@spinningarrow imageid and digest are the same because your GitHub Runner is still on buildx 0.7.1: https://github.com/spinningarrow/docker-action-test/runs/5758955970?check_suite_focus=true#step:5:59.

As you don’t have the setup-buildx-action step in your workflow, it will use the docker driver. Support for remote digest is in place since https://github.com/docker/buildx/pull/989 (buildx v0.8.0) for this driver.

Suggest to add the setup-buildx-action step to solve your issue while waiting for GitHub Runners to have the latest buildx in place:

      -
        name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
        with:
          version: v0.8.2

0reactions

nicorikkencommented, Aug 1, 2022

I encountered the same behavior where the digest output was actually the image ID. After installing Buildx I no longer get those outputs nor a digest returned in the JSON metadata output. I have decided to give up on digests with this action for now.