I’d like to get to a docker swarm sort of situation where I have 3 identical docker VMs, running 3 identical Caddy configurations, with 3 identical Apache VMs, and requests load balanced across them. And then I want a shared filesystem so the users can upload the files for their web sites to one location, and it’s made available to all the web front ends.

I’m currently in a mixed environment:

  • #xcpng on bare metal

  • FreeBSD VMs running important services (bastions, email, DNS)

  • #AlpineLinux VMs running docker for all my container-based stuff

So I’m trying to do the shared, highly available FS part of this design and I’d stay with FreeBSD if I could. #selfhosted

  • OversparkEnglish
    5·
    10 days ago

    Object storage (the S3 API stuff) is the most logical answer here, it’s much simpler and thus more reliable than solutions like Gluster, and the abstraction actually matches your use case. Otherwise something like an NFS share from a central fileserver works too.

    But I agree with the other comment that you’re trying to do kubernetes on hard mode and most likely with a worse result.