-
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
--export-cache option crashes buildkitd on custom frontend #1336
Comments
/cc @fermayo @tonyredondo |
@drodriguezhdez is there source code for |
Hi @tonistiigi, I created a repository with the minimum amount of code which reproduces this issue. Command:
Findings:It seems that if in the file
makes the But, if the second copy from Logs of the failed --export-cache
|
….6.4-15-gdc6afa0f) full diff: moby/buildkit@a7d7b7f...dc6afa0 - solver: avoid recursive loop on cache-export - fixes moby/buildkit#1336 --export-cache option crashes buildkitd on custom frontend - fixes moby/buildkit#1313 Dockerd / buildkit in a infinite loop and burning cpu - fixes / addresses moby#41044 19.03.9 goroutine stack exceeds 1000000000-byte limit - fixes / addresses moby#40993 Multistage docker build fails with unexpected EOF Signed-off-by: Sebastiaan van Stijn <[email protected]>
….6.4-15-gdc6afa0f) full diff: moby/buildkit@a7d7b7f...dc6afa0 - solver: avoid recursive loop on cache-export - fixes moby/buildkit#1336 --export-cache option crashes buildkitd on custom frontend - fixes moby/buildkit#1313 Dockerd / buildkit in a infinite loop and burning cpu - fixes / addresses moby/moby#41044 19.03.9 goroutine stack exceeds 1000000000-byte limit - fixes / addresses moby/moby#40993 Multistage docker build fails with unexpected EOF Signed-off-by: Sebastiaan van Stijn <[email protected]> Upstream-commit: e7c2b106ec7785fcb54b1cf80258a2bea25ed020 Component: engine
Hi,
I'm creating a PoC for a new buildkit frontend for Maven (which download the code and execute the tests).
It seems that the
--export-cache
option in thebuildctl
command is crashing thebuildkitd
container.After command enters into the export cache phase, it returns the following message
Killing the
buildkitd
container.Command to reproduce:
Using
export-cache type=registry
orinline
, it is obtaining the same error.Is it needed something specific in the frontend code to support this option
--export-cache
?Thank you so much.
The text was updated successfully, but these errors were encountered: