The main difference is that "containers" are chroots with their own PID
namespace, at least, while an ordinary chroot still keeps the PID numbering
from the host. In other words, the container has its own PID 1 – and
systemd really wants to be PID 1, as init. A container runtime such as
nspawn
Re: The question regarding missing dependencies.
You might try this:
*zcat /boot/initramfs-$(uname -r).img | grep -E "(depends|provides)"*
If you ran an update and dependencies were missing. Then
*update-initramfs -u*
wouldn't be of any help to you.
I hadn't introduced myself. My
On Di, 25.04.23 13:26, Benjamin Godfrey (mr.benjamingodf...@gmail.com) wrote:
> It seems I sent this to the wrong list. I hope this isn't off topic.
>
> Dear systemd mailing list,
>
> I am trying to finish the boot process for systemd inside the
> chroot.
systemd does not support booting in a
