# Running out of space - Docker image is large? **URL:** \ **Category:** Support\ **Created:** [May 30, 2026, 12:40am UTC](https://meta.discourse.org/t/running-out-of-space-docker-image-is-large/404122 "2026-05-30T00:40:02Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![long\_season](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/long_season/32/549854_2.png) [@long\_season](https://meta.discourse.org/u/long_season)\ **Post date:** [May 31, 2026, 7:20pm UTC](https://meta.discourse.org/t/running-out-of-space-docker-image-is-large/404122/4 "2026-05-31T19:20:54Z")
This is very informative, thanks. Before I try `cleanup`, does Discourse provide a way to verify backup integrity without doing a restore? The result of `du -hx / | sort -h | tail -49` (I found -h made it easier for me to parse the results): ```plaintext 833M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/42/fs/var/www/discourse/vendor/bundle/ruby 833M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/42/fs/var/www/discourse/vendor/bundle/ruby/3.4.0 837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var 837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www 837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse 837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse/vendor 837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse/vendor/bundle 837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse/vendor/bundle/ruby 837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse/vendor/bundle/ruby/3.4.0 839M /var/discourse/shared 839M /var/discourse/shared/standalone 840M /var/discourse 863M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/42 863M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/42/fs 868M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283 868M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs 874M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/284 874M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/284/fs 874M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/43 874M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/43/fs 908M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/263/fs/usr 925M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/22/fs/usr 944M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/263 944M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/263/fs 961M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/22 961M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/22/fs 1.3G /usr 1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251 1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251/fs 1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251/fs/var 1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251/fs/var/www 1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251/fs/var/www/discourse 1.5G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227/fs/var 1.5G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227/fs/var/www 1.5G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227/fs/var/www/discourse 1.6G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227 1.6G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227/fs 2.5G /var/log 2.5G /var/log/journal 2.5G /var/log/journal/1d9299c9656046d6bd0e18d4a09c183c 2.7G /var/lib/containerd/io.containerd.content.v1.content 2.7G /var/lib/containerd/io.containerd.content.v1.content/blobs 2.7G /var/lib/containerd/io.containerd.content.v1.content/blobs/sha256 9.8G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs 9.8G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots 13G /var/lib 13G /var/lib/containerd 17G /var 20G / ``` The output of `docker volume ls -qf dangling=true` was empty. Actually, `docker volume ls` is empty. `docker images -a`: ```plaintext IMAGE ID DISK USAGE CONTENT SIZE EXTRA discourse/base:2.0.20260209-1300 50d2dae489a9 4.77GB 1.12GB discourse/base:2.0.20260521-0047 27373b823bbe 4.89GB 1.17GB local_discourse/app:latest 01527763be8d 6.9GB 1.63GB U ``` I know too little about Docker to diagnose this output, but `/var/log/` seems a bit large if it’s just logs, and it’s interesting to have 3 images when I have just 1 forum running (maybe that is totally expected though). Appreciate the point about more storage space. I will probably expand, but this is a good learning experience before I do. --- _[View the full topic](https://meta.discourse.org/t/running-out-of-space-docker-image-is-large/404122)._