Selfhosted

60074 readers

777 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 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

[–] adam@kbin.pieho.me 1 points 2 years ago

The issue with orchestration is that you still need a way to share those small databases and config files.

Docker has ok NFS support so you'd want to move the files to NAS shares and have them mount those. Without some way to centralise or spread the files out you won't be covering your SSD failure case. Once you've got that going docker swarm will probably cover your needs just fine.

You could go with K8S but based on you setup that's a bit overkill (unless you're doing it as a learning exercise, in which case go nuts).