Re:“I just want to run a container”
by Klasiaster on Sunday October 02, 2016 @04:11PM
(#12623994)
It's still ok to also use rkt because it is compatible with machinectl+nspawn from systemd, in both directions.
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.
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`.