Selfhosted

40313 readers

237 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Best approach for Docker resilience with two hosts (self.selfhosted)

submitted 1 year ago by Sim 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 17 points 1 year 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 11 points 1 year 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 1 points 1 year 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)?

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

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

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

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

[–] Mio@feddit.nu 2 points 1 year ago

I think 3 nodes are required for that

[–] Sim 1 points 1 year ago (1 children)

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

[–] peter@feddit.uk 1 points 1 year ago

You can use your current docker I believe