-
Notifications
You must be signed in to change notification settings - Fork 581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
buildx failed with: error: failed to solve: blob not found #422
Labels
Comments
@mmeendez8 Thanks for your feedback. This issue is currently tracked in docker/buildx#681. |
lopopolo
added a commit
to artichoke/docker-artichoke-nightly
that referenced
this issue
Aug 9, 2021
There are still some bugs in the `gha` cache backend that are causing builds to fail: - docker/buildx#681 - docker/build-push-action#422 Removing caching until upstream resolves these issues.
PiDelport
added a commit
to ntls-io/nautilus-wallet
that referenced
this issue
Aug 31, 2021
There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling limits. Background reading: - buildx failed with: error: failed to solve: blob not found #422 docker/build-push-action#422 - Copy from previous stage fails #681 docker/buildx#681 - GHA export cache fails with mode=max #2276 moby/buildkit#2276 Try to work around this by limiting the overall concurrency to 1 for this workflow.
PiDelport
added a commit
to ntls-io/nautilus-wallet
that referenced
this issue
Sep 1, 2021
There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling limits. Background reading: - buildx failed with: error: failed to solve: blob not found #422 docker/build-push-action#422 - Copy from previous stage fails #681 docker/buildx#681 - GHA export cache fails with mode=max #2276 moby/buildkit#2276 Try to work around this by limiting the overall concurrency to 1 for this workflow.
PiDelport
added a commit
to ntls-io/nautilus-wallet
that referenced
this issue
Sep 1, 2021
There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling limits. Background reading: - buildx failed with: error: failed to solve: blob not found #422 docker/build-push-action#422 - Copy from previous stage fails #681 docker/buildx#681 - GHA export cache fails with mode=max #2276 moby/buildkit#2276 Try to work around this by limiting the overall concurrency to 1 for this workflow.
PiDelport
added a commit
to ntls-io/nautilus-wallet
that referenced
this issue
Sep 1, 2021
There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling limits. Background reading: - buildx failed with: error: failed to solve: blob not found #422 docker/build-push-action#422 - Copy from previous stage fails #681 docker/buildx#681 - GHA export cache fails with mode=max #2276 moby/buildkit#2276 Try to work around this by limiting the overall concurrency to 1 for this workflow.
PiDelport
added a commit
to ntls-io/nautilus-wallet
that referenced
this issue
Sep 2, 2021
There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling limits. Background reading: - buildx failed with: error: failed to solve: blob not found #422 docker/build-push-action#422 - Copy from previous stage fails #681 docker/buildx#681 - GHA export cache fails with mode=max #2276 moby/buildkit#2276 Try to work around this by limiting the overall concurrency to 1 for this workflow.
Should be fixed docker/buildx#681 (comment). If you encounter this kind of issue with GHA cache please open an issue on BuildKit repo. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Troubleshooting
Before submitting a bug report please read the Troubleshooting doc.
Behaviour
Steps to reproduce this issue
Expected behaviour
Build and push image caching layers.
Actual behaviour
Configuration
Logs
build_docker.zip
The text was updated successfully, but these errors were encountered: