Here is disk space usage after a Docker install on Digital Ocean:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vda1 30830588 7049764 22191688 25% /
none 4 0 4 0% /sys/fs/cgroup
udev 498084 4 498080 1% /dev
tmpfs 101788 348 101440 1% /run
none 5120 0 5120 0% /run/lock
none 508940 1164 507776 1% /run/shm
none 102400 0 102400 0% /run/user
That’s 5.3% of the 30GB drive.
Here’s what a new DO droplet looks like at launch with nothing on it:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vda1 30830588 1625676 27615776 6% /
none 4 0 4 0% /sys/fs/cgroup
udev 498084 4 498080 1% /dev
tmpfs 101788 324 101464 1% /run
none 5120 0 5120 0% /run/lock
none 508940 0 508940 0% /run/shm
none 102400 0 102400 0% /run/user
Subtracting the new droplet state from the installed state, it looks like a Discourse install takes 5,424,088 or 5.4 GB.
(I also forgot that we set up a 2GB swap as a part of the install on a 1GB droplet, so that might mean the Discourse usage is less…)
The 30GB drive goes from 6% used before the install to 25% used after the install.
It’s possible bootstrapping may take more temp disk space as stuff is built, though. The smallest DO instance is 20GB disk space so we we would not have seen an issue.