Issue with push to GHCR - buildx failed with: error: failed to solve: failed to copy: cannot reuse body, request must be retried
See original GitHub issueTroubleshooting
Before submitting a bug report please read the Troubleshooting doc.
Behaviour
Steps to reproduce this issue
- Start the run via GH Actions to build and push a new image for two architectures to GitHub packages
- Error occurs in more than 50% of the runs
GitHub status was green when executing the run
Expected behaviour
The build and push should push the new image(s) to the GitHub registry
Actual behaviour
The build works, but pushing the image results in the error
buildx failed with: error: failed to solve: failed to copy: cannot reuse body, request must be retried
This is also reported in #452 which was closed referencing the GH issue this morning. However the error also occurs when the GH packages are in operational state. As proposed here is a new issue for the same error with the logs attached
Configuration
- Repository URL (if public): https://github.com/SAP-samples/btp-setup-automator
- Build URL (if public): https://github.com/SAP-samples/btp-setup-automator/actions/runs/2421754052
- Workflow: https://github.com/SAP-samples/btp-setup-automator/blob/main/.github/workflows/docker-build-and-push.yml
Logs
Attached: log_build_and_push.txt
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:14 (3 by maintainers)
Top Results From Across the Web
GAR error "cannot reuse body, request must be retried" #452
I have read TROUBLESHOOTING.md . I wasn't sure from the "Cannot push to a registry" section whether your preference is for issues to...
Read more >Workaround for manifest unknown failure to pull the images ...
You can verify whether the image failed to pull is existing or not on the RH registry using "SHA256" Digest through "skopeo inspect"...
Read more >Resolve the Amazon ECS error when pulling Docker images ...
How do I resolve the “error pulling image configuration: error parsing HTTP 403 response body” error in Amazon ECS when pulling a Docker...
Read more >Troubleshooting | Container Registry documentation
ERROR : (gcloud.docker) A Docker command did not run successfully. Tried to run: 'docker push gcr.io/container-engine-docs/example' Exit code: 1.
Read more >Example workflows - Docker Documentation
This page showcases different examples of how you can customize and use the Docker GitHub Actions in your CI pipelines. Push to multi-registries...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We have sent a message to the GitHub team about this issue. Will keep you in touch.
I put a thread here on the discourse, hoping it’s a better way to make it googleable and to provide evidence it’s not just us. @jauderho @lechnerc77 if you’d like to reply or +1 it that might help? The thread. https://github.community/t/ghcr-repeatedly-fails-during-docker-image-push-failed-to-solve-cannot-reuse-body-request-must-be-retried/254087