<div dir="auto"><div>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 will also delegate a cgroup subtree to the container, which systemd also needs (being rather strongly built around cgroups).</div><div dir="auto"><br></div><div dir="auto">So they're chroots with a few additional features needed to "boot" an init system.<br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Wed, Apr 26, 2023, 20:09 Benjamin Godfrey <<a href="mailto:mr.benjamingodfrey@gmail.com">mr.benjamingodfrey@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Re: The question regarding missing dependencies. <div><br></div><div>You might try this:</div><div><br></div><b><font color="#ff0000">zcat /boot/initramfs-$(uname -r).img | grep -E "(depends|provides)"</font></b><br><div><br></div><div>If you ran an update and dependencies were missing. Then </div><div><br></div><div><b><font color="#ff0000">update-initramfs -u</font></b><br></div><div><b><font color="#ff0000"><br></font></b></div><div><font color="#000000">wouldn't be of any help to you. </font></div><div><font color="#000000"><br></font></div><div><font color="#000000">I hadn't introduced myself. My background is in art and literature, I started working on the front end, and I started moving to the backend to troubleshoot problems with the web server. Learning NodeJs, Php and Bash, and I'm learning C++. In particular, I'm trying to get the Apache2 to serve. I have Ubuntu working on a Chromebook. </font></div><div><font color="#000000"><br></font></div><div><font color="#000000">Is it really that much more complicated to complete the boot process in chroot? I'll try the container solution. </font></div><div><font color="#000000"><br></font></div><div><font color="#000000">yours truly,</font></div><div><font color="#000000">Benjamin Godfrey</font></div><div> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 26, 2023 at 5:00 AM <<a href="mailto:systemd-devel-request@lists.freedesktop.org" target="_blank" rel="noreferrer">systemd-devel-request@lists.freedesktop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send systemd-devel mailing list submissions to<br> <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">systemd-devel@lists.freedesktop.org</a><br> <br> To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br> or, via email, send a message with subject or body 'help' to<br> <a href="mailto:systemd-devel-request@lists.freedesktop.org" target="_blank" rel="noreferrer">systemd-devel-request@lists.freedesktop.org</a><br> <br> You can reach the person managing the list at<br> <a href="mailto:systemd-devel-owner@lists.freedesktop.org" target="_blank" rel="noreferrer">systemd-devel-owner@lists.freedesktop.org</a><br> <br> When replying, please edit your Subject line so it is more specific<br> than "Re: Contents of systemd-devel digest..."<br> <br> <br> Today's Topics:<br> <br> 1. Re: Failed to start up manager. Freezing execution. (Caeri Tech)<br> 2. Completing the boot process for systemd inside the chroot<br> (Benjamin Godfrey)<br> 3. Re: Completing the boot process for systemd inside the<br> chroot (Lennart Poettering)<br> <br> <br> ----------------------------------------------------------------------<br> <br> Message: 1<br> Date: Tue, 25 Apr 2023 09:18:35 -0400<br> From: Caeri Tech <<a href="mailto:caeritech@gmail.com" target="_blank" rel="noreferrer">caeritech@gmail.com</a>><br> To: Lennart Poettering <<a href="mailto:lennart@poettering.net" target="_blank" rel="noreferrer">lennart@poettering.net</a>><br> Cc: <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">systemd-devel@lists.freedesktop.org</a><br> Subject: Re: [systemd-devel] Failed to start up manager. Freezing<br> execution.<br> Message-ID:<br> <CAAuiGE=<a href="mailto:hGC%2Br3sYjkJBt7Vfin-s8B4kkUAsFhfCAGKmYdOYWbg@mail.gmail.com" target="_blank" rel="noreferrer">hGC+r3sYjkJBt7Vfin-s8B4kkUAsFhfCAGKmYdOYWbg@mail.gmail.com</a>><br> Content-Type: text/plain; charset="utf-8"<br> <br> Interesting. If I downgrade systemd and systemd-libs from 253 to 252 it<br> works as before.<br> <br> Is there perhaps a dependency that I'm now required to include in the<br> initramfs config?<br> <br> On Tue., Apr. 25, 2023, 4:54 a.m. Lennart Poettering, <<br> <a href="mailto:lennart@poettering.net" target="_blank" rel="noreferrer">lennart@poettering.net</a>> wrote:<br> <br> > On Di, 25.04.23 01:43, Caeri Tech (<a href="mailto:caeritech@gmail.com" target="_blank" rel="noreferrer">caeritech@gmail.com</a>) wrote:<br> ><br> > > *:: running cleanup hook [udev]*<br> ><br> > This ouput doesn't look as if systemd was actually involved?<br> ><br> > > But it still freezes execution.<br> > ><br> > > The rescue and emergency shells do not start if I activate the hook and<br> > > again it freezes. The shells do start, however, when the hook is not<br> > > activated.<br> ><br> > Anyway, without debug logs as suggested in my earlier mail this is<br> > really hard to debug. Enable debug logging.<br> ><br> > Lennart<br> ><br> > --<br> > Lennart Poettering, Berlin<br> ><br> -------------- next part --------------<br> An HTML attachment was scrubbed...<br> URL: <<a href="https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/9ba4216c/attachment-0001.htm" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/9ba4216c/attachment-0001.htm</a>><br> <br> ------------------------------<br> <br> Message: 2<br> Date: Tue, 25 Apr 2023 13:26:08 -0700<br> From: Benjamin Godfrey <<a href="mailto:mr.benjamingodfrey@gmail.com" target="_blank" rel="noreferrer">mr.benjamingodfrey@gmail.com</a>><br> To: <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">systemd-devel@lists.freedesktop.org</a><br> Subject: [systemd-devel] Completing the boot process for systemd<br> inside the chroot<br> Message-ID:<br> <<a href="mailto:CAJxCLXpVJiCk9MbsjndjN_y0R9m8-4hAbW5XXK3fFXSUWF4TNQ@mail.gmail.com" target="_blank" rel="noreferrer">CAJxCLXpVJiCk9MbsjndjN_y0R9m8-4hAbW5XXK3fFXSUWF4TNQ@mail.gmail.com</a>><br> Content-Type: text/plain; charset="utf-8"<br> <br> It seems I sent this to the wrong list. I hope this isn't off topic.<br> <br> Dear systemd mailing list,<br> <br> I am trying to finish the boot process for systemd inside the chroot. I<br> have followed the instructions in the documentation, but I am still having<br> some problems.<br> <br> The following is typical output:<br> <br> [...$ sudo systemctl start systemd-journald<br> Running in chroot, ignoring request: start...] ### Showing that systemd is<br> bailing out because of the chroot.<br> <br> [...$ ps --no-headers -o comm 1<br> init...] ### showing the Chromebook is using init at PID 1<br> <br> [...$ file /sbin/init<br> /sbin/init: symbolic link to /lib/systemd/systemd ...} ### showing that<br> init and systemd are linked in the chroot.<br> <br> [...$ stat /sbin/init<br> <br> File: /sbin/init -> /lib/systemd/systemd ...] ### Showing that systemd is<br> in use.<br> <br> {...$ ls /usr/lib/systemd } ### Shows the systemd files are loaded.<br> <br> [...$ systemctl is-active --quiet service<br> System has not been booted with systemd as init system (PID 1). Can't<br> operate.<br> Failed to connect to bus: Host is down ...] *### Systemd not active in<br> chroot*<br> <br> <br> *I'm wondering if adding a line in the rc would help complete the boot<br> process. *<br> <br> <br> Can you please help me troubleshoot this issue?<br> <br> Thank you for your time.<br> <br> yours truly,<br> <br> Benjamin Godfrey<br> -------------- next part --------------<br> An HTML attachment was scrubbed...<br> URL: <<a href="https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/2dd09d88/attachment-0001.htm" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/2dd09d88/attachment-0001.htm</a>><br> <br> ------------------------------<br> <br> Message: 3<br> Date: Wed, 26 Apr 2023 10:33:44 +0200<br> From: Lennart Poettering <<a href="mailto:lennart@poettering.net" target="_blank" rel="noreferrer">lennart@poettering.net</a>><br> To: Benjamin Godfrey <<a href="mailto:mr.benjamingodfrey@gmail.com" target="_blank" rel="noreferrer">mr.benjamingodfrey@gmail.com</a>><br> Cc: <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">systemd-devel@lists.freedesktop.org</a><br> Subject: Re: [systemd-devel] Completing the boot process for systemd<br> inside the chroot<br> Message-ID: <ZEjh6FduyO+JPRaf@gardel-login><br> Content-Type: text/plain; charset=us-ascii<br> <br> On Di, 25.04.23 13:26, Benjamin Godfrey (<a href="mailto:mr.benjamingodfrey@gmail.com" target="_blank" rel="noreferrer">mr.benjamingodfrey@gmail.com</a>) wrote:<br> <br> > It seems I sent this to the wrong list. I hope this isn't off topic.<br> ><br> > Dear systemd mailing list,<br> ><br> > I am trying to finish the boot process for systemd inside the<br> > chroot.<br> <br> systemd does not support booting in a classic chroot(). Use a<br> container manager for that, for example "systemd-nspawn -D<br> /some/directory -b"<br> <br> Lennart<br> <br> --<br> Lennart Poettering, Berlin<br> <br> <br> ------------------------------<br> <br> Subject: Digest Footer<br> <br> _______________________________________________<br> systemd-devel mailing list<br> <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">systemd-devel@lists.freedesktop.org</a><br> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br> <br> <br> ------------------------------<br> <br> End of systemd-devel Digest, Vol 156, Issue 26<br> **********************************************<br> </blockquote></div> </blockquote></div></div></div>