3 ms·
Probably because chroot does not expose some sort of low-level knob that systemd relies on to work. They had to make their own implementation of that in systemd
by mariusor 2y ago
Probably because chroot does not expose some sort of low-level knob that systemd relies on to work. They had to make their own implementation of that in systemd-nspawn, have a look at that.
- Xeamek 2y agoYes, but to use systemd-nspawn, your host must be running systemd to begin with.