That sounds like your local network IP’s are conflicting with the default docker IP addresses.
What is your routers subnet?
That sounds like your local network IP’s are conflicting with the default docker IP addresses.
What is your routers subnet?
Ahhhh now you’re talking kubernetes.
I mean you can do it with 2 machines and docker compose, but yeah.
If you have a docker compose, you can just bring it to a new machine with the storage medium and hit “go” and it’ll go.
That’ll probably be enough for a home setup and have a 1 hr downtime in a failure.
If you want “always hot” kubernetes is basically “multi-node docker on cocaine “
Damn, that addiction is strong lol.
I’m happy to help where I can but it’s a FUCKTON of knowledge and setup to go far enough to kubernetes it.
Docker-compose is 100x easier and gets you 95% of what you need.
You are going to want a single larger server and docker
Much easier maintenance
If you’re crazy, you’ll go with Kubernetes . I personally recommend it., I love it.
But I also work in it every day, so there’s a convenience there, but the complexity is off the charts .
Not a bad idea, but I’ll warn you that the addiction for homelabs is strong.
The n100 will make you sad eventually as your self-hosting addiction soars.
An older i5 with onboard gpu or an nvidia card will make you happier and not pull THAT much wattage.
Your Minecraft server will thank you.
Gotta pay the bills somehow, and I’m just happy they care about privacy.
Check what your docker subnets are, but that shouldn’t conflict.