User avatar
Norm (ノーム) CastoriceBlushing @norm@shrimp.biribiri.dev
1w
Don't think I've seen much people actually use systemd-nspawn instead of docker/podman or an lxc based solution
4
0
1
0
User avatar
Emelia/Emi @becomethewaifu@tech.lgbt
1w
@norm Those three are great, but they make too many assumptions for certain uses to be viable.

I use systemd-nspawn as a better substitute for chroot stuff that's practically a VM, which docker doesn't really work with. (For workloads that I'd normally put in a full VM, rather than a minimalistic docker container)
1
0
2
0
User avatar
Norm (ノーム) CastoriceBlushing @norm@shrimp.biribiri.dev
1w
@becomethewaifu I've been using LXC for those sorts of workloads. What makes sytemd-nspawn better for that use case?
1
0
0
0
User avatar
Emelia/Emi @becomethewaifu@tech.lgbt
1w
@norm In that case it's entirely because I learned about nspawn first. I barely even know LXC exists, so haven't tried to replace my existing stack with it.

I don't exactly like systemd, but given that it's what debian ships with, might as well use the features it offers... (It's also unironically the best DHCPv6-PD client I've used outside of "appliance OSes" like openwrt, since every other solution seems to involve brittle shell script 'glue' to delegate the assigned prefix to radvd, that aren't packaged by most distros I know, so you have to copy-paste-debug them from archwiki or similar)
0
0
2
0