I’m running Docker on Ubuntu server; around 50 containers running, most admin via Portainer. Configuration files and small databases for container applications are stored on the local SSD, media and larger files are stored on a NAS.

NAS data and the container folders are backed up.

I have a second identical machine doing nothing. What would you recommend researching to add resilience to this setup? Top priority is quick and easy restoration should the SSD fail - everything else is relatively easy to replace.

I’ll create an SSD RAID but I like the idea of a second host.

Big P
link
fedilink
English
171Y

You can use docker swarm (or a better container orchestrator) to have the containers automatically fail over to the second host

Matt The Horwood
link
fedilink
English
111Y

Swarm will also spread the load out over both hosts, but all your data would need to be accessible by both hosts

@Sim@lemmy.nz
creator
link
fedilink
English
11Y

Thanks. That means I need to move all data off the hosts on to, say, a NAS - then the NAS becomes the single point of failure. Can I operate a swarm without doing that but still duplicate everything from host 1 to host 2, so host 2 could take over relatively seamlessly (apart from local DNS and moving port forwarding to nginx on the remaining host)?

Matt The Horwood
link
fedilink
English
21Y

Yes could sync the 2 hosts data, you also can use both hosts as nginx upstreams.

@Still@programming.dev
link
fedilink
English
21Y

I think you can run a ceph or glusterfs cluster for sharing files in a cluster

@Mio@feddit.nu
link
fedilink
English
21Y

I think 3 nodes are required for that

@Sim@lemmy.nz
creator
link
fedilink
English
11Y

Thanks. Can I use my existing, single Docker to start a new swarm, or do I have to start from scratch?

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 279 users / day
  • 589 users / week
  • 1.34K users / month
  • 4.55K users / 6 months
  • 1 subscriber
  • 3.5K Posts
  • 70K Comments
  • Modlog