Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
arxkdev opened this issue Jan 8, 2025 · 2 comments
Open

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

arxkdev opened this issue Jan 8, 2025 · 2 comments

Comments

@arxkdev
Copy link
Contributor

arxkdev commented Jan 8, 2025

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.
logs

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

@arxkdev arxkdev added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 8, 2025
@peaklabs-dev
Copy link
Member

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?

@peaklabs-dev peaklabs-dev removed the 🔍 Triage Issues that need assessment and prioritization. label Jan 13, 2025
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Jan 13, 2025
@arxkdev
Copy link
Contributor Author

arxkdev commented Jan 14, 2025

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%.

@github-actions github-actions bot removed the 🐛 Bug Reported issues that need to be reproduced by the team. label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants