Conversation

I really want to like Docker Swarm - it's *very nearly* a simple alternative to K8s, but is sadly missing a few things I would really, really like:

* Can create config-maps! But they're immutable - if you want to change it you need to delete the associated stacks, delete the config, create the config, create the stack 😬
* Can't assign static IPs. I realise that's a bit awkward with a "create N replicas" thing, but something like "10.0.0.[1-4]" would be great.

2
0
0

* Changing the IP address of a machine breaks Swarm. Force-leaving the swarm and re-joining breaks networking for *every* container on the node, even if they're not using Swarm! They *all* have to be force-recreated, ideally in the right order.
* Non-swarm Containers can join Swarm networks… except for Docker Compose on a follower node (you can attach it after, but…😕 )
* Smaller bugs - even on leaders, compose can't attach to a Swarm network - another container has to do it first.

0
0
0

@ipsi Have you thought about trying out Nomad?

1
0
0

@alpha I have not, though I will look into it! Docker is working well enough that I'm not *desperately* looking for alternatives, but it would definitely be nice.

I was giving serious thought to taking leave of my senses and spinning up Proxmox + K8s 🤯

1
0
0

@ipsi There’s no chance in hell I want to run k8s for personal infra again, but Ansible+docker containers isn’t really cutting it either. I’ve been idly considering Nomad, but that also seems like more overhead than I need, so now I’m seriously considering Nix instead. (At my scale, I want pets.)

1
0
0

@alpha Yeah, it's a tricky one. Docker is a bit *too* simple, K8s is *way* too much.

Nomad seems interesting, will have to dig into it when I have more functional braincells, although I suspect it's a bit too much as well. On the other hand, it *does* support iSCSI, which means I could plonk configuration volumes on the NAS (sqlite is very common and doesn't play well with NFS/etc).

1
0
0

@ipsi Seems to be the case for a whole slew of things, really, including our previous commiseration on logging infrastructure.

0
0
0