3 ms·
Think it's a "process Graph"... and Process ID 1 is systemd on the[/her] machine. Edit: turns Out, she explains: [...]systemd: rkt will run a program called sys
by darfs 10y ago
Think it's a "process Graph"... and Process ID 1 is systemd on the[/her] machine.
Edit: turns Out, she explains:
[...]systemd: rkt will run a program called systemd-nspawn as the init (PID 1) process inside your container. This is because it can be bad to run an arbitrary process as PID 1[0] -- your process isn't expecting it and will might react badly. It also run some systemd-journal process? I don't know what that's for yet.[...]"
[0] https://engineeringblog.yelp.com/2016/01/dumb-init-an-init-for-docker.html https://engineeringblog.yelp.com/2016/01/dumb-init-an-init-f...
- tadfisher 10y agoThe 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 agoI grepped the Link above from the article. But yea, first look, it seems usefull :-)
- Klasiaster 10y agoIt's still ok to also use rkt because it is compatible with machinectl+nspawn from systemd, in both directions.
- tadfisher 10y agoIn 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.