Build Service is maxing out CPU usage even though the app is only allowed 50% of resources

[msbt]

I'm using the build service to build a custom image. The last step, when it starts to compile everything, almost brings down the whole server, meaning all Couldron apps and system view become unresponsive, because it uses all available CPU power. I've tried setting it to 50%, which would mean it's only allowed to use 4 cores of the available 8, but as soon as it's running, it will max out all cores. The build-app itself shows almost no CPU usage (0.something%), but the system view shows this:

Any suggestions on how to limit the resources so this won't happen?

Sidenote: the link with the questionmark in Cloudron in the apps/resources view points to https://docs.cloudron.io/apps/#cpu-quota which is not working anymore, the current one is https://docs.cloudron.io/apps/#cpu-limit

[nebulon]

Looks like the cpu quota does not apply to the docker containers which the build service spins off to actually build images. It uses the docker addon, which is certainly not ideal as it can have side-effects like this on other apps. I guess we didn't design the build service to run on mission critical Cloudrons which are not only setup for image building....

[msbt]

Ah yeah, that's what I thought. Moved the build app to somewhere else. Would be nice to add --cpu-quota to the build command to mirror the apps settings (from https://dev.to/code42cate/dont-build-docker-apps-without-this-flag-48kg)