#I was wondering if it is possible for
versed lagoon
Oh boy, looks like it's an open issue since 5 years. https://github.com/moby/buildkit/issues/593
abstract wasp
I think that functionality actually was merged at some point: https://github.com/sipsma/buildkit/blob/9624ab4710dd1a63453cc028802c9992b9715f3c/client/llb/state.go#L411-L411
Not documented of course (same as most of buildkit)
And it would require setting up cgroups ahead of time on the buildkit host
versed lagoon
Sneaky 😄 Is that a global setting i.e all builds would have those limits or configurable per build? If so, can we make it configurable via Dagger API?
abstract wasp
Sneaky 😄 Is that a global setting i.e all builds would have those limits or con...
It would be per-build I believe. It's technically possible to expose it in the Dagger API but we have been generally hesitant to directly expose APIs like this that rely on something on the host being setup beforehand. The problem being that it results in queries that work on one host but not another. That being said, it probably would be possible to expose this, I just think we'd have to look into presenting as an API like "limit query to x cpus, N MB memory" rather than "have query use this cgroup setup ahead of time on the host"