Selfhosted

60281 readers

860 users here now

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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Best approach for Docker resilience with two hosts (lemmy.nz)

submitted 2 years ago by Sim@lemmy.nz to c/selfhosted@lemmy.world

17 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] peter@feddit.uk 15 points 2 years ago (2 children)

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

[–] mhzawadi@lemmy.horwood.cloud 9 points 2 years ago (1 children)

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 1 points 2 years ago (2 children)

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)?

[–] Still@programming.dev 2 points 2 years ago (1 children)

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

[–] Mio@feddit.nu 2 points 2 years ago

I think 3 nodes are required for that

[–] mhzawadi@lemmy.horwood.cloud 2 points 2 years ago

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

[–] Sim@lemmy.nz 1 points 2 years ago

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