actions/docker-build-push
actions/docker-build-push
3
0
Fork 0
mirror of https://gitea.com/docker/build-push-action.git synced 2024-11-25 02:49:39 +01:00
Code Issues Projects Activity Pipelines
docker-build-push/TROUBLESHOOTING.md
CrazyMax 65a1a173ac
Move to dedicated md 
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
2020-09-21 21:06:04 +02:00

1.3 KiB
Raw Blame History

Troubleshooting

Errors on pushing to registry

While pushing to a registry, you may encounter these kinds of issues:

  • failed commit on ref "layer-sha256:...": invalid content digest in response: invalid checksum digest format
  • failed commit on ref "layer-sha256:...": no response
  • failed commit on ref "manifest-sha256:...": unexpected status: 401 Unauthorized
  • unexpected response: 401 Unauthorized

These issues are not directly related to this action but are rather linked to buildx, buildkit, containerd or the registry on which you're pushing your image. The quality of error message depends on the registry and are usually not very informative.

To help you solve this, you should first enable debugging in the setup-buildx action step:

  -
    name: Set up Docker Buildx
    uses: docker/setup-buildx-action@v1
    with:
      buildkitd-flags: --debug

Next you can test pushing with containerd using this workflow. Do not forget to set ctr --debug for the pushing step. If it works then open an issue on buildkit repository.