Unexpected Storage Growth After Repeated Container Builds in Dokploy

[ardhichoiruddin]

I’m experiencing a significant increase in storage usage every time I build a container in Dokploy. I’ve already run the following cleanup commands:

docker system prune -a
docker builder prune -a
docker image prune -a

However, the reduction in disk usage is minimal. Ideally, the storage footprint should decrease after removing old build artifacts, but it keeps growing with each new build.

What could be causing this behavior in Dokploy? Are there specific caches, build layers, volumes, or internal directories that need to be cleaned manually? And how can I ensure that Dokploy fully frees up storage after repeated build processes?