3 ms·

The systemd-nspawn manual might be more useful here: https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html https://www.freedesktop.org/software/s

The systemd-nspawn manual might be more useful here: https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html https://www.freedesktop.org/software/systemd/man/systemd-nsp... Personal opinion: If you're already using systemd on the host, nspawn containers are trivially easy to create, boot, and maintain. Running systemd as the guest init allows you to use `systemctl -M <machine>` and `journalctl -M <machine>` the same way you would for the host, and the guest process tree is exposed in the host's `systemctl status`.

darfs 10y ago
I grepped the Link above from the article. But yea, first look, it seems usefull :-)
Klasiaster 10y ago
It's still ok to also use rkt because it is compatible with machinectl+nspawn from systemd, in both directions.
- tadfisher 10y ago
  In this case, rkt (or CoreOS?) eschews the more advanced features that rely on btrfs in favor of an overlayfs solution, so it's not a complete abstraction.