System resource limitations

[awderz4]

I’ve been experiencing an issue during deployments where system resources (CPU/RAM) spike significantly. In some cases, this leads to overall server instability or even downtime.

It seems that while resource limits are applied to running containers, these limits are not respected during the build/deployment phase.

It would be extremely helpful if:

Resource limits (CPU, memory) could also be enforced during deployments/builds
Or there was an option to configure separate resource limits specifically for the deployment process

This would help prevent deployments from exhausting system resources and improve overall reliability, especially in production environments.

Thanks in advance!

[Cinzya]

The problem lies on Docker itself. As far as I've heard, Docker Buildkit doesn't support this yet, and Coolify relies on Buildkit for some features.
There is already a open PR for it moby/buildkit#6569

[djsisson]

You have to build using a container driver, not the default.
This let's you set limits, although you can create this yourself and tell buildx to use it, coolify only runs docker build rather than docker buildx build command which always uses the default.
You could probably use a custom build command in coolify, but compose build also only uses the default not a custom builder that has been created