build(docker): intermittent ghcr push failures

[nitrocode]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Overview of the Issue

Upon merge, pushing new images to ghcr will randomly fail.

https://github.com/runatlantis/atlantis/actions/workflows/atlantis-image.yml?query=is%3Afailure

Seems like its related to buildkit v0.11.0, which is related to a containerd issue, which docker-build-push action uses. Pinning buildkit should resolve this issue.

Reproduction Steps

It's difficult to reproduce. Seems to happen randomly. Rerunning succeeds.

Others have reproduced it using buildkit v0.11.0 and able to avoid it using v0.10.6

Logs

#43 exporting to image
#43 pushing layers 3.0s done
#43 ERROR: failed to push ghcr.io/runatlantis/atlantis:dev-debian: failed to copy: io: read/write on closed pipe
------
 > exporting to image:
------
ERROR: failed to solve: failed to push ghcr.io/runatlantis/atlantis:dev-debian: failed to copy: io: read/write on closed pipe
Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/runatlantis/atlantis:dev-debian: failed to copy: io: read/write on closed pipe

Source https://github.com/runatlantis/atlantis/actions/runs/3973612428/jobs/6812382380

Additional Context

• buildx failed with: ERROR: failed to solve: failed to push ghcr.io/finchsec/kali:latest: failed to copy: io: read/write on closed pipe docker/build-push-action#761
• "failed to copy: io: read/write on closed pipe" on ctr images push while pushing large images containerd/containerd#7972
• issue came from pr fix retry when writer is reset on push containerd/containerd#6995