[Bug]: Disk Usage after a build on builder server stays high (>70%)

[arxkdev]

Error Message and Logs

No errors (network or console).

No errors/problems in mycoolify.com/horizon

Steps to Reproduce

1. Ensure you have a builder server
2. Deploy an app using your builder server
3. Check Disk Usage on Build Server, should continue really high (mine was 73%)
4. Disk Usage only comes down once the cleanup cron is ran (or triggered manually)

Example Repository URL

No response

Coolify Version

v4.0.0-beta.380

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

When building my application using my builder server, disk goes up really high and never gets cleaned up until the cleanup cron is ran or triggered manually.

Currently my workaround is to just to either:

• Trigger the cleanup manually once the build finishes.
• or bring the cleanup cron down to every 10-30 minutes.

Did not even realize it had 73% disk used until logs told me.

[peaklabs-dev]

This is because the build server is only there to build you image, like GitHub Action can do, the images and also the rest of the resources are still stored on you hosting server where you stuff is hosted so the disk usage will be high there. Or what exactly is you issue?

[arxkdev]

This is because the build server is only there to build you image, like GitHub Action can do, the images and also the rest of the resources are still stored on you hosting server where you stuff is hosted so the disk usage will be high there. Or what exactly is you issue?

The problem I'm having is on the Build Server. The Disk Usage goes up when I build (which is fine), but it continues to rise as I re-deploy my app more and more, almost as if it's not finding the already existing cache.

For example if I start with around ~8% Disk Usage:
I run a build, it goes to 15%
I run another build, it goes to 20%
I run another build, it goes to 30%
and so on.. until it gets to 100%.

[tolstenko]

The cleaning process is not fully working right now on 390. I just discovered the docker builder prune freed 133gb here.

[marwie]

Hello, we're currently still on 379 and it seems like the cleanup doesn't reduce the disc usage at all right now

Manual Docker cleanup job executed successfully. Disk usage before: 100%, Disk usage after: 100%.

It seems like it's not fixed in later versions?