User david reports high disk usage on a 30GB droplet, with /lib/docker consuming 18.2GB (9.7GB in overlay, 8.1GB in devicemapper). He questions whether 9.7GB for overlay is normal and whether it’s safe to delete the obsolete devicemapper folder after switching storage drivers. Falco suggests docker system prune, but david finds it ineffective, reclaiming 0B despite showing 1.7GB reclaimable images. He manually deletes /var/lib/docker/devicemapper without issues [4]. sam questions if du is double-counting layered data; david confirms du handles hard links correctly, ruling out duplication as the cause. Others share similar experiences: angus links to a fix involving Docker cleanup, and blau details a multi-step cleanup (reinstalling Docker, running launcher cleanup, and docker system prune) that recovered 5.4GB. sam suggests nuking /var/lib/docker entirely as a last resort. Dev_Work asks for a plugin to monitor disk space and email alerts — no solution provided. The thread highlights Docker storage bloat as a common issue, especially after rebuilds or driver changes, and offers manual cleanup as the most reliable fix.
Is 9.7GB an “normal” level of usage for the overlay folder?
Now that I moved from devicemapper to overlay, does anyone know if it’s safe to delete the devicemapper folder? Or do I need to run a docker command to clean it up somehow?
I was low on disk space and could not upgrade discourse nor free up space. Turns out /var/lib/docker/aufs/diff was the culprit. This is what worked for me:
upgrade system software, autoremove, autoclean and reboot to new kernel;
I was on an old 17.x docker version and after several ./launcher rebuild app I had less than 5GB free on a 20 GB disk. Same issue as discussed here (thread closed):
Sometimes what I do is just junk /var/lib/docker altogether and start from scratch (stop docker and all containers first, we store nothing important there), perhaps try that.