buildkit
buildkit copied to clipboard
moby
Add build cgroup settings
We should be able to specify resource limits per build with buildkit.
Is there any news when and if this will be implemented? With Buildkit we constantly get out of memory errors and errors that /tmp/tmp... can't be found which I guess is a reason of low memory and probably OOM killing.
We're also having an issue with BuildKit during builds on Azure DevOps. During the final task of exporting layers, the CI kills the task with an error code of 137. Being able to limit the memory usage would allow us to use BuildKit.
We also need more memory for building or windows containers with buildkit. How in the word is this not a issue of more people?
Has anyone figured out how to set memory on docker compose using buildkit? Disabling buildkit using environment variables or setting it to false in daemon.json does not seem to work on Docker for Windows. Is there any other workaround?
This hits hard and is a major drawback from using BuildKit. "classic" docker build command supports --memory flags and equivalent for CPU, but not BuildKit. It makes BuildKit very limited for enterprise usage. Can you please provide an update on this?
Possible to re-title this to capture the Windows aspect too, since cgroup can easily mislead the Windows folks?
Since we closed https://github.com/docker/for-win/issues/13860 in favor of this. @nicks
more and more users are adopting buildkit to run it in their Azure Pipelines, so now we see quite a few errors like "Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)", although buildkit already has 6GB RAM - this is unusable
