-
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
Build function: ResourceExhausted: grpc: received message larger than max (_ vs. 4194304) #5217
Comments
Same with a container builder I guess? https://docs.docker.com/build/drivers/docker-container/ |
Signed-off-by: Pierre Fenoll <[email protected]>
Note I get a "failed to solve" as well as a "Build function": https://productionresultssa7.blob.core.windows.net/actions-results/df31ae2f-cf73-48e2-8a72-9437dc860981/workflow-job-run-7a6d4a80-403f-515f-0b06-639e26161515/logs/job/job-logs.txt?rsct=text%2Fplain&se=2024-08-06T22%3A54%3A21Z&sig=wFPjzixxo1TSJYJbtvJsTYu8GfoZL56np9icEIuceyo%3D&ske=2024-08-07T09%3A57%3A30Z&skoid=ca7593d4-ee42-46cd-af88-8b886a2f84eb&sks=b&skt=2024-08-06T21%3A57%3A30Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2024-05-04&sp=r&spr=https&sr=b&st=2024-08-06T22%3A44%3A16Z&sv=2024-05-04
Nope! It doesn't reproduce! docker buildx create --name=sprgrn --bootstrap --driver=docker-container --driver-opt=image=docker.io/moby/buildkit:buildx-stable-1
Could it just be passing because of BuildKit's patch release?
Note however that the failing call is extracted from a larger program that makes many such calls. To make sure this passes I launched a whole run (which passed) then re-extracted the call listed in this issue. # Within https:/fenollp/supergreen
# Switch to the branch of https:/fenollp/supergreen/pull/71 (commit bc03702c)
# You should have stable Rust installed (e.g. 1.80)
BUILDX_BUILDER=your-builder ./hack/clis.sh audit clean Side Q: what can I do to make this (fully cached buildx call) faster? I see it takes inside of 1-4s |
I don't think so, this might be related to #4948 (comment) Looks like this will be fixed on next Moby release: moby/moby#48242 (cc @thaJeztah) |
@crazy-max not sure; after my PR, Tonis noticed that it may have been redundant as that specific error already showed that it had the right sizes set; see moby/moby#48242 (comment) |
Ok then there is smth else that needs to be fixed on moby side I assume as this works with a container builder. |
This was fixed with moby/moby#48242 (repro in here is 5MB, not 44 like in moby/moby#48242 (comment)) |
Continuation of #4948
gix-b4db05e0408bd73f.Dockerfile.txt
The text was updated successfully, but these errors were encountered: