yis, systemd-nspawn, still the goat. one main advantage i think is running long running containers, that have a full systemd running inside them (multiprocess). docker is horrible at multiprocess. and with that type of thing, you can have agents running inside that handle incremental updates and things are just easier this way vs trying to go 100% single process. having a single process is not a requirement for microservices and it eats into the uptime having to be a single proc wrangler.
haproxy is a good example, it has really, really good hot-reloading. and docker won't let it do that.
it's just cgroups, and volumes are bind mounts for your persistent data. fast. very.
Login to reply
Replies (2)
Very very true, but how are you handling automation, packaging or IAC? Also when I say: containers != docker. Fuck docker specifically.
I've been using fuse.bindfs and podman to handle my complex filesystem needs. I don't need anything multi process at the moment. However the git server will for now.
yeah, i highly recommend nspawn as a tool for containers without the docker, kubernetes or other cloud grief.
also, sorry, not sorry, but i'm not deploying a hello world to amazon. ever.
it's such an anti-bitcoin thing to do, if you ask me.
especially someone like @ChipTuner who could build a cloud from scratch, i mean, did, if i am understanding what he says correctly.