I’m trying to set up Discourse via Docker installation on a ovh.com VPS (VPS Classic 1, 10 GB HDD, 1 GB RAM). Sadly during bootstrapping Discourse at some point I always get no space left on device. Before bootstrapping I had 8GB free space. This is really a lot. Is there a way to get the bootstra…

There’s nothing wrong with the script, it was tested by another user just two days prior. 94: read -p "Enter the name of your domain [ex: www.webeindustry.com] " domain; 95: sed -i "s/"www.example.com"/$domain/g" discourse.conf; It seems you’ve skipped this part.

I really had the wrong domain set up but I changed it the HOSTNAME in /var/www/discourse/config/discourse.conf rebooted but still get the same error.

Crazy thought: can you please paste the output from sudo dumpe2fs /dev/ploop10158p1 About the only idea I have left is that for some reason the block size of your filesystem is abnormally large. That would cause everything to appear to take up much more space…

Can’t use dumpe2fs: dumpe2fs 1.42.12 (29-Aug-2014) dumpe2fs: Operation not permitted while trying to open /dev/ploop41512p1 Couldn't find valid filesystem superblock.

OK, rather than trying to guess what the actual filesystem type is, can you please paste the contents of your /etc/fstab?

[Bild] mshappe: /etc/fstab proc /proc proc defaults 0 0 none /dev/pts devpts rw 0 0 none /dev/shm tmpfs rw 0 0 cgroup /cgroups/blkio cgroup blkio 0 0 cgroup /cgroups/memory cgroup memory 0 0 cgroup /cgroups/devices cgroup freeze…

Hm. OK. Apparently OpenVZ makes this sort of thing more opaque than we might like, since that tells me nothing about /dev/ploop* :smile: How about cat /proc/mounts?

My Discourse instance has run out of 25GB of space (Linode 1024 VPS). The only files over 100MB were 7 backups, 225MB each, and one 700MB nginx log file. Hardly adding up to 2.5GB. When I ran ./launcher cleanup, more than 10GB were freed up. Clearly there’s a leak somewhere. I’d be curious how muc…

If you are using device mapper, you are in a world of pain and suffering. Strongly not recommended. We block install on device mapper for a reason.

Can't install Discourse with only 10 GB disk, run out of space

Support Self-hosting

gerhard (Gerhard Schlager) 16. Februar 2016 um 13:14 34

Usage of devicemapper is not recommended. I don’t think that has changed in the last few months.

https://meta.discourse.org/t/why-is-docker-devicemapper-taking-so-much-hard-drive-space/34378/11?u=gerhard

Thema		Antworten	Aufrufe
You have less than 5GB of free space on the disk. You will need more space to continue Self-hosting server-resources	7	3585	18. Oktober 2023
Docker installation not working Self-hosting	16	5435	4. November 2016
Discourse image and installation size. Clean /var/lib/docker/overlay2? Self-hosting server-resources	10	4566	28. Juli 2021
Getting Discourse installed on OVH VPS Self-hosting	26	9081	13. Januar 2015
Discourse upgrade fails due to insufficient disk space on 25G droplet Self-hosting server-resources	38	2083	30. März 2022

Can't install Discourse with only 10 GB disk, run out of space

Verwandte Themen