Github Actions fails at Create and Push Manifest File step of tag_manifest job

[alexiswl]

Action

See action: https://github.com/umccr/RNAsum/actions/runs/5041902971/jobs/9043544763#step:4:224

Error

Error was: ghcr.io/umccr/rnasum:0.4.7-linux-amd64 is a manifest list

Notes

Other things to note:

• The actual build process completed.
• Docker image exists under packages but not in the same format as previous packages.
• An 'unknown' tag exists in the packages section.

If we search the 'unknown' tag's shasum (e6eabc12c3e7e2d38e09fe833aa1116db1253fbe19931055e0c28b03e60f5a3d) in the GitHub Actions logs we can see that we have the following lines:

2023-05-22T06:43:44.1758218Z #27 exporting manifest sha256:35cd38b09f7c67703956ab33333e7fb14b012146644e49d384c72c16dafec347 done
2023-05-22T06:43:44.1758696Z #27 exporting config sha256:44352c1564f4e6ba18ff987523d774c0c5b9125bd15e0403d9671e10178308d1 done
2023-05-22T06:43:44.1759213Z #27 exporting attestation manifest sha256:e6eabc12c3e7e2d38e09fe833aa1116db1253fbe19931055e0c28b03e60f5a3d done
2023-05-22T06:43:44.1759668Z #27 exporting manifest list sha256:78d1dc34868c253c036f9824e9f21266806e3f324c9e68ca928be12a4b14d89e done

And that even though this is the build step for the linux/amd64 architecture, we have exported a manifest list?

Related Issues

• Default image output in buildx v0.10 cannot be pushed to Yandex Cloud Container Registry docker/buildx#1513
• GitHub Action produces unknown architecture and OS docker/build-push-action#820
• GitHub Action "docker/build-push-action" produces unknown architecture and OS ghusta/docker-fakesmtp#4

Suggested solutions

From the issues above, it is suggested that we add 'provenance: false' to our buildx setup.

It may also be worth upgrading some of the GH Action versions at the same time.