Buildx gRPC ResourceExhausted error – looking for guidance / best practices #1442
Unanswered
RushiChandalia
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi folks 👋
We’re running into a recurring issue with docker/build-push-action@v5 + Buildx/BuildKit and wanted to start a discussion to see if others have hit the same problem and whether there are recommended solutions or best practices.
❌ The issue
Our builds occasionally fail with the following error:
From what we understand, this is due to BuildKit’s internal gRPC message size limit (~16MB) being exceeded.
🧱 Context
Example snippet (simplified):
with:
context: ./service
file: ./service-package.Dockerfile
tags: my-image:latest
Using ChatGPT and other resources I was able to get this recommended fixes:
For Solution 1 I am not able to find any documentation on how to use that env variable and where to use it.
And for solution 2, this feels more like a workaround than a real solution. (Because we want to keep metadata with the build)
🤔 What we’re hoping to understand
Is there any supported way (now or planned) to:
chunk or stream large metadata
raise the gRPC limit safely
avoid sending large attestations over gRPC entirely?
Are there recommended best practices for:
large repos / monorepos
builds with many dependencies
Is disabling SBOM/provenance the intended solution in these cases, or just a known limitation today?
Appreciate any insights from maintainers or others who’ve run into this 🙏
Happy to provide more details if useful.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions