- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
You must log in or register to comment.
I’m just going to point out that besides containers, systemd can now manage virtual machines:
systemd version we added systemd-vmspawn. It’s a small wrapper around qemu, which has the point of making it as nice and simple to use qemu as it is to use nspawn.
The idea is that we provide a roughly command line equivalent interface to VMs as for containers, so that it really is as easy to invoke a VM as it already is to invoke a container, supporting both boot from DDIs and boot from directories.
That actually could be really handy. I’ll have to check it out once this release moves downstream.
Yeah, meanwhile I’ll keep using LXD / Incus for both containers and VMs.
Incus has a few advantages: an image repository, a nicer container manager (cli tools) and sane security defaults. By default Incus assumes your containers should be isolated and secure environments while
systemd-nspawnis more about quick and dirty containers useful to compile something or run some trusted task.The thing with Incus is that you get the image repository and manager and the permissions applied to containers make them isolated and secure environments by default running on another user etc etc
This is really hard to read.
Yeah, I was typing from my phone while being distracted by other people. Fixed now.
Thanks, that’s much easier to read. :)
Systemd can manage containers!? TIL
systemd really wants to do everything
Yes 😂 😂 😂
The dream of GNU/Systemd is real.
Perhaps one day it’ll just be systemd at this rate
