3
0
Fork 0
mirror of https://gitea.com/docker/build-push-action.git synced 2024-11-22 09:29:38 +01:00

Merge pull request #348 from crazy-max/doc

Update troubleshooting notes
This commit is contained in:
CrazyMax 2021-04-25 00:12:32 +02:00 committed by GitHub
commit 4cef7b9d89
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -16,16 +16,8 @@ These issues are not directly related to this action but are rather linked to [b
[buildkit](https://github.com/moby/buildkit), [containerd](https://github.com/containerd/containerd) or the registry [buildkit](https://github.com/moby/buildkit), [containerd](https://github.com/containerd/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. 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 To help you solve this, you have to [enable debugging in the setup-buildx](https://github.com/docker/setup-buildx-action#buildkit-container-logs)
[setup-buildx action step](https://github.com/docker/setup-buildx-action): action step and attach BuildKit container logs to your issue.
```yaml
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v1
with:
buildkitd-flags: --debug
```
Next you can test pushing with [containerd action](https://github.com/crazy-max/ghaction-setup-containerd) using the Next you can test pushing with [containerd action](https://github.com/crazy-max/ghaction-setup-containerd) using the
following workflow. If it works then open an issue on [buildkit](https://github.com/moby/buildkit) repository. following workflow. If it works then open an issue on [buildkit](https://github.com/moby/buildkit) repository.