4 ms·
I went with Docker Swarm on the same advice from someone else, and tbh, it's unnecessary overhead as well. And at least on RPis, it's very fragile and not as se
by jyrkesh 4y ago
I went with Docker Swarm on the same advice from someone else, and tbh, it's unnecessary overhead as well. And at least on RPis, it's very fragile and not as self-healing as I'd hope it to be. My stacks are well compartmentalized, but weird database locks will still happen, or the swarm will just become unreachable, and I gotta go power-cycle a node or two to get things back up again. (I mean, we're talking once every few weeks or something, but still not okay.)
I've been moving workloads to an old gaming rig running NixOS with varying levels of isolation (some containers, but really just good user/group/permissions management), and it runs super well.
Of course, you could do the same with just Docker Compose and no Swarm, and I think you'd still be better off than using Swarm.
- vineyardmike 4y agoYea I had a not dissimilar experience. I didn’t have as many issues, but I pretty quickly realized a single old gaming Pc was way easier than a half dozen Pis stacked up in the closet trying to coordinate. Auto scaling and balancing seem nice at work… but complexity was rarely needed at home. The main reasons swarm is better than other options for clustering IMO is networking. They can be set up to share the ports on all devices and map it back to the correct container on whatever host it’s on, so you can disconnect the target IP:Port from the container.