I have a 25g droplet, which Discourse claims should be big enough, but I cannot do the upgrade to the latest version as I’ve run out of storage. My forum is very small with very little traffic. I ran ./launcher cleanup and even deleted old backups, but still no joy. What can I do? root@DO-Discourse:/var/discourse# ./launcher rebuild app x86_64 arch detected. WARNING: We are about to start downloading the Discourse base image This process may take anywhere between a few minutes to an hour, depending on your network speed Please be patient 2.0.20220224-2005: Pulling from discourse/base 5eb5b503b376: Pull complete 35b2f73fc27b: Pull complete 44526e3ec669: Pull complete Digest: sha256:8a8bb9525882220196c0faa8ce95c62a7fb607fc203d4247b3d5985f3ca9c3d8 Status: Downloaded newer image for discourse/base:2.0.20220224-2005 docker.io/discourse/base:2.0.20220224-2005 You have less than 5GB of free space on the disk where /var/lib/docker is located. You will need more space to continue Filesystem Size Used Avail Use% Mounted on /dev/vda1 25G 22G 3.0G 88% / Would you like to attempt to recover space by cleaning docker images and containers in the system? (y/N)y If the cleanup was successful, you may try again now root@DO-Discourse:/var/discourse#

I think it’s safe to delete all of those images. If you need them they’ll get replaced when you rebuild. Taking a snapshot isn’t a bad idea. What I’d do it just spin up a new instance; that’s safest, and probably faster than a snapshot, but if knowing how to do that isn’t fun or instructive, your idea is fine.

[image] Simon_Manning: du -h -s /* | sort -h -r 18G /var du -h -s /var/* | sort -h -r 14G /var/lib 2.8G /var/log 933M /var/discourse du -h -s /var/lib/* | sort -h -r 13G /var/lib/docker 744M /var/lib/snapd root@DO-Discourse:/var/discourse# du -h -s /var/lib/docker/* | sort -h -r 13G /var/lib/docker/overlay2 16M /var/lib/docker/image root@DO-Discourse:/var/discourse# du -h -s /var/lib/docker/overlay2/* | sort -h -r 8.7G /var/lib/docker/overlay2/d319d95263d87c2a75a4bc9a9f03a25ea7f6eb1f7bac687e7ae7d45522939dc0 2.8G /var/lib/docker/overlay2/79be56509f1588c272683332ef50abd54f0aeb06d0e2d13f8eea1bace3b3db46 873M /var/lib/docker/overlay2/5b148cbbcca894be512c7407568104cd7b2e3d48ab7b7d74c6c0f731806cdddc Any point going further?

Deleted 2.8G of logs, which only got me to 4.9G. Don’t have a “test” instance to try ./launcher rebuild app --skip-prereqs Any other suggestions? Is it simply not possible to run a discourse instance on a 25G droplet anymore?

See the end of Prune unused Docker objects | Docker Docs I think you want to prune all and prune volumes

docker system prune --volumes WARNING! This will remove: - all stopped containers - all networks not used by at least one container - all volumes not used by at least one container - all dangling images - all dangling build cache Are you sure you want to continue? [y/N] y Total reclaimed space: 0B root@DO-Discourse:/# Any other suggestions?

[image] AndyBr: Any point going further? Not really, that’s pretty telling that the space is being consumed by docker for your container(s). After a cleanup, my numbers are very similar to yours which is perhaps (but not necessarily) indicative of it just being how much it uses. [image] AndyBr: Is it simply not possible to run a discourse instance on a 25G droplet anymore? I did have problems with a 25GB Linode however that was with 500MB+ backups, deleting two or three backups gave me enough room to rebuild. I opted to move to the next tier with 50GB because it was only going to become more constraining and I wanted to rebuild on a monthly cron job. That was before the switch to Ember CLI though, could that have made things significantly bigger?

That 9GB overlay seems like the issue. But I have one on of a similar size on another instance I just checked. It’s always been challenging at 25GB. I’d recommend that you bite the bullet and get more SSD. The next thing you could try would be to see if there is OS-level stuff that you can remove (logs, unneeded programs, indexes from find, maybe?). Another idea would be to just spin up a new 25GB VM and move there, hoping that whatever filled up the old one won’t be a problem this time. None of these answers seems especially satisfying. I fought hard with a 25GB droplet on one or two instances I help manage in the last week or two, but I think you’ve done everything that I did.

[image] Benjamin_D: do you have any use for snap ? Not sure. Do I need it for a discourse-only installation? And if not, how do I delete it?

[image] AndyBr: Do I need it for a discourse-only installation? I don’t think so :thinking: after a full backup download, you could snap list to check what snaps are installed, and if none sudo apt purge snapd

root@DO-Discourse:/var/discourse# snap list Name Version Rev Tracking Publisher Notes core18 20220309 2344 latest/stable canonical✓ base core20 20220304 1376 latest/stable canonical✓ base lxd 4.0.9-8e2046b 22753 4.0/stable/… canonical✓ - snapd 2.54.4 15177 latest/stable canonical✓ snapd root@DO-Discourse:/var/discourse#

Discourse upgrade fails due to insufficient disk space on 25G droplet

Product Support Self-hosting

AndyBr (Andy) March 30, 2022, 7:31pm 39

Deleted one of the images and that did the trick!

Thank you everyone for all your help.

Topic		Replies	Views
Discourse image and installation size. Clean /var/lib/docker/overlay2? Self-hosting server-resources	10	4696	July 28, 2021
My website is always down Self-hosting	46	2909	April 22, 2022
Unable to rebuild discourse due to no space left on device Self-hosting	32	3779	November 19, 2022
Running out of space - Docker image is large? Product Support	9	579	June 1, 2026
Any advice on how to save space? Self-hosting server-resources	24	2467	January 26, 2023

Discourse upgrade fails due to insufficient disk space on 25G droplet

Related topics