-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ResourceExhausted: grpc: received message larger than max (_ vs. 4194304) #4948
Comments
/cc @fenollp |
Hello @thompson-shaun @thaJeztah @tonistiigi & others! I seem to be experiencing this again: I can send more info, just: Am I running this patched code? I have no idea. Could it be related to moby/moby#48164 (comment) ? My config:
|
There was a comment on the patch for that for that specific case, the patch probably had no effect; moby/moby#48242 (comment). Your error shows a different size though, so possibly it's related to the fix in the BuildKit Dockerfile parsing; #4969. Feel free to open a separate ticket if you're able to reproduce the issue. |
Transfer from docker/buildx#2453
...
Description
Maybe related: docker/buildx#2208
Expected behaviour
As this Dockerfile is generated in the same way as many others, I'd expect the build to not fail on transport error but maybe on my own logic error.
Actual behaviour
The error:
Buildx version
github.com/docker/buildx v0.14.0 171fcbe
Docker info
Builders list
Configuration
Command:
Huge Dockerfile: huge_Dockerfile.txt
Build logs
Additional info
Note I adapted the call so you can reproduce, but doing so I removed some correct
--build-context=..
to refer to some empty directory. This does not have any effect on the reported error, which seems to happen soon enough.The text was updated successfully, but these errors were encountered: