Up next in my series on how and what I #SelfHost: #Storage

I've talked about my #UnRaid server before, my VMs run on there. The built-in docker is added to my Docker Swarm, so it gets assigned containers from the swarm to run.

I also run a #GlusterFS cluster of 3 nodes across the two laptop SSDs (plus one arbiter VM). I run things like my Docker Registry backed onto Gluster, so the images are still available if any one node is down. Overall, I find Gluster slow, and its broken on me a couple times, but it does what I need it to do.

Ultimately, if a docker container requires storage, it will usually get Gluster (and the container run on the laptops), unless it has special IO requirements. Things like SQLite databases will corrupt themselves on Gluster or NFS. So I use deployment placement constraints to hold some docker workloads on my UnRaid server.

In the past, I ran containers anywhere, and they would volume-mount NFS or CIFS to UnRaid, but I ran into a "Stale File Handle" problem -- where containers would randomly have their volumes fail under them, and it would corrupt databases, leave processes stuck in IOWait, etc. No matter what I did, what protocol I used, etc, it would always eventually have problems.

I also run #GarageHQ S3 on my UnRaid server, though I haven't found a great use for it yet. I really want to run #WeedFS, as I like the design and architecture, but likewise haven't found a use case.

🏷️ #SelfHosting