A user, Ironclad14, reports that Docker is consuming space on their 20GB root partition, while the majority of their storage is on a separate /home partition. The discussion explores solutions to free up space without resizing partitions. Suggestions include configuring Discourse to use external storage for uploads, backups, and databases, as well as mounting /var/lib/docker on a dedicated partition. thabbs provides a step-by-step guide for moving Docker’s data directory to a new partition, while sam shares a configuration using Docker volumes. techAPJ offers a detailed guide based on using DigitalOcean block storage, which has been tested successfully. The thread concludes with Ironclad14 planning to try the solution on a fresh install.
Can you let me know of any way I can make use of more space without having to resize partitions? It’s risky business while they’re mounted and data loss isn’t something anyone likes to deal with.
Do we have a howto for this @techapj? That is, configuring Discourse to use another drive for the high storage requirement items like the database, file/image uploads, backups, etc?
Basically I keep /var/postgres_data in root and then mount /var/discourse/shared/ on the second volume, additionally I put docker containers in /var/discourse/shared/docker
There are many ways of skinning this, just keep postgres_data on the fastest drive and you should be good.
Does this mean my summary interpretation is also on the right track?
I’m not sure if a test droplet is the best way to go, in my case. The IPs will be different, I’d have to setup a new host, and even if I did all that, nginx would be completely off… I’m pretty sure this would be even-more confusing. I’d probably be better off just making a backup before I change anything.
Based on @sam’s suggestion I spun up a new droplet → installed Discourse → added a block storage volume → moved uploads and backups to that volume. Everything worked out fine. Here is the howto: