[storrgie]

I like how there is an implied influence (e.g. dockerism) about containers being immutable/ephemeral... meanwhile I've been incredibly happy moving most of my VM deployments over to nspawn because many standards of systems management were anti-patterns in dockerland.

[Zancarius]

Oh hey, another nspawn user. I've had really good luck using it for isolation purposes as well, and it's really handy for testing clean builds (arch-nspawn comes to mind, but it's also really useful for simulating installs without using a full VM).

I'm curious what extra tools, if any, you've used for nspawn (automation or otherwise). In my experience, it's been pretty easy to manage just with the default tools but it seems images can be a bit fiddly if you deviate too far from the host OS or anything without systemd--although I can't imagine that'd be useful outside experimentation or testing.

[masterleep]

systemd-nspawn certainly deserves more acclaim. It's great, and really easy to use right out of the box.

[drewlander]

Absolutely agree. No need for anything fancy, quick and easy to setup and use.

[unethical_ban]

nspawn looks cool. Seems like a copy of LXC. I agree with you; containers don't have to be ephemeral. Using them like lightweight, snapshottable VMs on a bridged network is good for quick and dirty hosting.