# Can't install Discourse with only 10 GB disk, run out of space
**URL:** https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149
**Category:** Self-hosting
**Tags:** docker, server-resources
**Created:** [22 مايو 2015، 7:27م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149 "2015-05-22T19:27:54Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@hedgehog](https://meta.discourse.org/u/hedgehog)
#### Post date: [22 مايو 2015، 10:38م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/21 "2015-05-22T22:38:51Z")
You can select Ubuntu 14.04 with docker as your operating system.
---
### Author:  [@pl3bs](https://meta.discourse.org/u/pl3bs)
#### Post date: [22 مايو 2015، 10:41م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/22 "2015-05-22T22:41:44Z")
Yea, I just did some checking and see that docker is now supported with the latest openvz kernels.
[https://openvz.org/Docker\_inside\_CT](https://openvz.org/Docker_inside_CT)
[https://openvz.org/Download/kernel/rhel6-testing/042stab105.4](https://openvz.org/Download/kernel/rhel6-testing/042stab105.4)
Not sure what your issue is. Sorry.
---
### Author:  [@hedgehog](https://meta.discourse.org/u/hedgehog)
#### Post date: [23 مايو 2015، 11:19ص UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/23 "2015-05-23T11:19:07Z")
@pl3bs: I tried your Dockerless installation script on the OVH-host but I got problems with it as well.
I filed this bug in your repo: [Connection refused while connecting to upstream · Issue #6 · nahtnam2/dontdockmebro · GitHub](https://github.com/pl3bs/dontdockmebro/issues/6)
---
### Author:  [@pl3bs](https://meta.discourse.org/u/pl3bs)
#### Post date: [23 مايو 2015، 12:14م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/24 "2015-05-23T12:14:18Z")
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.
---
### Author:  [@hedgehog](https://meta.discourse.org/u/hedgehog)
#### Post date: [23 مايو 2015، 1:24م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/25 "2015-05-23T13:24:03Z")
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.
---
### Author:  [@mshappe](https://meta.discourse.org/u/mshappe)
#### Post date: [23 مايو 2015، 1:36م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/26 "2015-05-23T13:36:46Z")
Crazy thought: can you please paste the output from
```plaintext
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…
---
### Author:  [@hedgehog](https://meta.discourse.org/u/hedgehog)
#### Post date: [24 مايو 2015، 12:39م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/27 "2015-05-24T12:39:45Z")
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.
```
---
### Author:  [@mshappe](https://meta.discourse.org/u/mshappe)
#### Post date: [24 مايو 2015، 9:11م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/29 "2015-05-24T21:11:40Z")
OK, rather than trying to guess what the actual filesystem type is, can you please paste the contents of your `/etc/fstab`?
---
### Author:  [@hedgehog](https://meta.discourse.org/u/hedgehog)
#### Post date: [24 مايو 2015، 9:52م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/30 "2015-05-24T21:52:57Z")
> [@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 freezer,devices 0 0 cgroup /cgroups/cpuset cgroup cpuacct,cpu,cpuset 0 0`
---
### Author:  [@mshappe](https://meta.discourse.org/u/mshappe)
#### Post date: [24 مايو 2015، 9:56م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/31 "2015-05-24T21:56:49Z")
Hm. OK. Apparently OpenVZ makes this sort of thing more opaque than we might like, since that tells me nothing about `/dev/ploop*` 😄 How about `cat /proc/mounts`?
---
### Author:  [@dandv](https://meta.discourse.org/u/dandv)
#### Post date: [16 فبراير 2016، 12:38م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/33 "2016-02-16T12:38:26Z")
My Discourse instance has run out of 25GB of space (Linode 1024 VPS). The only [files over 100MB](http://unix.stackexchange.com/a/259051/29324) 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 much disk space Docker takes up on other folks’ similar configurations. Right now, I have
```plaintext
root@localhost:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 24G 7.4G 16G 33% /
devtmpfs 494M 4.0K 494M 1% /dev
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 100M 340K 99M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 496M 0 496M 0% /run/shm
none 100M 0 100M 0% /run/user
/dev/mapper/docker-8:0-41527-352bef0[...] 9.8G 1.5G 7.8G 17% /var/lib/docker/devicemapper/mnt/352bef0[...]
```
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [16 فبراير 2016، 1:14م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/34 "2016-02-16T13:14:19Z")
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](https://meta.discourse.org/t/why-is-docker-devicemapper-taking-so-much-hard-drive-space/34378/11)
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [16 فبراير 2016، 6:41م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/35 "2016-02-16T18:41:06Z")
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.
---
### Author:  [@dandv](https://meta.discourse.org/u/dandv)
#### Post date: [17 فبراير 2016، 5:07م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/36 "2016-02-17T17:07:12Z")
Well, I never did anything intentional or specific to end up with devicemapper. Never saw a warning, let alone been blocked from installing.
I installed Discourse around June 2015 (I think - is there a way to tell specifically?), so maybe devicemapper was the default back then for Docker on Linode kernels, after [Docker dropped the aufs requirement](https://blog.docker.com/2013/11/docker-0-7-docker-now-runs-on-any-linux-distribution/)? I’m running Ubuntu 14.04.3 LTS (GNU/Linux 4.4.0-x86\_64-linode63 x86\_64) and have upgraded the Linode to KVM from Xen.
1. What exactly does this “world of pain” entail? Is it worth restoring a Discourse backup to an instance running on aufs?
2. Should there be some guidance in the [30-minute installation guide](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) about aufs? Right now it assumes DigitalOcean, but folks may want to install on other hosts, for whatever reason.
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [17 فبراير 2016، 9:27م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/37 "2016-02-17T21:27:13Z")
> [@dandv](#):
>
> What exactly does this “world of pain” entail? Is it worth restoring a Discourse backup to an instance running on aufs?
The short version: It will work fine until it suddenly corrupts the file system; and then demons fly out of your nose, circle back behind you and strangulate you. Only one of these is an overstatement 😉
Here are a few memorable quotes from the world of pain:
> [@sam](#):
>
> We had some very nasty support issues that were incredibly hard to troubleshoot.
> [@What is the best docker storage backend to use on a VPS?](https://meta.discourse.org/t/what-is-the-best-docker-storage-backend-to-use-on-a-vps/34646/5):
>
> Never, ever use device mapper. That is a one way ticket to corruption town, sooner or later. It is buggy as hell and has been for a year despite Red Hat saying “it works now” over and over.
> [@What is the best docker storage backend to use on a VPS?](https://meta.discourse.org/t/what-is-the-best-docker-storage-backend-to-use-on-a-vps/34646/7):
>
> I don’t know but you can ask the support customer whose corrupted install on Centos (and thus devicemapper) we just had to recover via a backup..
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [17 فبراير 2016، 10:27م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/38 "2016-02-17T22:27:57Z")
> [@dandv](#):
>
> Should there be some guidance in the 30-minute installation guide about aufs? Right now it assumes DigitalOcean, but folks may want to install on other hosts, for whatever reason.
I am pretty sure launcher warns about non aufs these days.
>
---
### Author:  [@dandv](https://meta.discourse.org/u/dandv)
#### Post date: [18 فبراير 2016، 6:59ص UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/39 "2016-02-18T06:59:30Z")
> [@sam](#):
>
> I am pretty sure launcher warns about non aufs these days.
Not a peep actually. I’ve just installed on a Ubuntu 14.04 LTS Linode. Here’s the full log.
[Installing Discourse on Linode - Pastebin.com](http://pastebin.com/68wRhftD)
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [18 فبراير 2016، 10:11م UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/40 "2016-02-18T22:11:44Z")
What is `docker info` returning?
---
### Author:  [@dandv](https://meta.discourse.org/u/dandv)
#### Post date: [19 فبراير 2016، 1:57ص UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/41 "2016-02-19T01:57:37Z")
```plaintext
root@localhost:~# docker info
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 2
Server Version: 1.10.1
Storage Driver: devicemapper
Pool Name: docker-8:0-98371-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: ext4
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 2.075 GB
Data Space Total: 107.4 GB
Data Space Available: 19.82 GB
Metadata Space Used: 1.974 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.146 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.77 (2012-10-15)
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.4.0-x86_64-linode63
Operating System: Ubuntu 14.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 991.7 MiB
Name: localhost
ID: WYHE:UE4G:DVLD:BQNI:2QRX:WTK6:ZDRP:MQOM:QWAP:F2C5:7N7D:CEXH
WARNING: No swap limit support
```
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [19 فبراير 2016، 1:59ص UTC](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/42 "2016-02-19T01:59:59Z")
So odd … any idea why that test [Can't install Discourse with only 10 GB disk, run out of space - #38 by sam](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149/38) is not running, try putting some `echo` commands in launcher to see if its even hitting it?
[Previous page](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149.md?page=1)
[Next page](https://meta.discourse.org/t/cant-install-discourse-with-only-10-gb-disk-run-out-of-space/29149.md?page=3)