Disk space getting eaten up by build cache #6726
Replies: 4 comments
-
i can confirm the same, the space gets eaten up on each app deploy. i think dokku should be handling this internally or explictly state in the docs to do system prune from time to time |
Beta Was this translation helpful? Give feedback.
-
Similar issue here. I see my disk usage from the last two years go up and down, suggesting that Dokku was cleaning up after itself. We upgraded Dokku last December, and the disk usage only goes up unless we use the docker prune commands. This is mostly an issue with our development Dokku (v0.33.9) that hosts our review apps. Those apps are constantly being created and destroyed, but there are a bunch of lingering files in |
Beta Was this translation helpful? Give feedback.
-
I wonder if we're getting a bunch of little cache hits because of the new dockerfile image builds that are used to tag images now (and add code etc.). I might be able to get away with adding a |
Beta Was this translation helpful? Give feedback.
-
I occasionally run |
Beta Was this translation helpful? Give feedback.
-
We've got a server which has a front-end nextjs application. A back-end flask application, and a postgres db instance all running on a dokku instance. We recently upgraded (3-4 months or so) from an older version of dokku (I think it was 0.25.6) to the latest. At the same time, we upgraded our hosting server on DigitalOcean to a more recent version of Ubuntu to support the latest version of Dokku.
We've started running into an issue where we run out of disk space when pushing our apps to our dokku box. We don't recall ever running into this on our older version of dokku. We did have a larger disk drive on the older Ubuntu box (250gb vs 80gb now). But we were running on the old box for almost 3 years without ever running into this issue. And we now have run into this disk space issue after only a few months.
We narrowed the issue down to build cache. When running
df
we can see our drive usage tick up after just about every push to dokku.And running
docker system prune -a
clears up space and gets us from 90%+ back down to 14% usage.Is this normal? It's unclear if it's related to the updated or just coincidental. But it doesn't seem like something that we should have to monitor as closely as we are having to do now. We didn't see any other issues/discussions around this when searching, but it doesn't seem like anything we're doing is different enough that no one else would be running into this too?
Any thoughts?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions