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).
So they're chroots with a few additional features needed to "boot" an init system.
On Wed, Apr 26, 2023, 20:09 Benjamin Godfrey <mr.benjamingodfrey@xxxxxxxxx> wrote:
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. Thenupdate-initramfs -uwouldn't be of any help to you.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.Is it really that much more complicated to complete the boot process in chroot? I'll try the container solution.yours truly,Benjamin GodfreyOn Wed, Apr 26, 2023 at 5:00 AM <systemd-devel-request@xxxxxxxxxxxxxxxxxxxxx> wrote:Send systemd-devel mailing list submissions to
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
or, via email, send a message with subject or body 'help' to
systemd-devel-request@xxxxxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
systemd-devel-owner@xxxxxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of systemd-devel digest..."
Today's Topics:
1. Re: Failed to start up manager. Freezing execution. (Caeri Tech)
2. Completing the boot process for systemd inside the chroot
(Benjamin Godfrey)
3. Re: Completing the boot process for systemd inside the
chroot (Lennart Poettering)
----------------------------------------------------------------------
Message: 1
Date: Tue, 25 Apr 2023 09:18:35 -0400
From: Caeri Tech <caeritech@xxxxxxxxx>
To: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: Failed to start up manager. Freezing
execution.
Message-ID:
<CAAuiGE=hGC+r3sYjkJBt7Vfin-s8B4kkUAsFhfCAGKmYdOYWbg@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Interesting. If I downgrade systemd and systemd-libs from 253 to 252 it
works as before.
Is there perhaps a dependency that I'm now required to include in the
initramfs config?
On Tue., Apr. 25, 2023, 4:54 a.m. Lennart Poettering, <
lennart@xxxxxxxxxxxxxx> wrote:
> On Di, 25.04.23 01:43, Caeri Tech (caeritech@xxxxxxxxx) wrote:
>
> > *:: running cleanup hook [udev]*
>
> This ouput doesn't look as if systemd was actually involved?
>
> > But it still freezes execution.
> >
> > The rescue and emergency shells do not start if I activate the hook and
> > again it freezes. The shells do start, however, when the hook is not
> > activated.
>
> Anyway, without debug logs as suggested in my earlier mail this is
> really hard to debug. Enable debug logging.
>
> Lennart
>
> --
> Lennart Poettering, Berlin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/9ba4216c/attachment-0001.htm>
------------------------------
Message: 2
Date: Tue, 25 Apr 2023 13:26:08 -0700
From: Benjamin Godfrey <mr.benjamingodfrey@xxxxxxxxx>
To: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Completing the boot process for systemd
inside the chroot
Message-ID:
<CAJxCLXpVJiCk9MbsjndjN_y0R9m8-4hAbW5XXK3fFXSUWF4TNQ@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
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. I
have followed the instructions in the documentation, but I am still having
some problems.
The following is typical output:
[...$ sudo systemctl start systemd-journald
Running in chroot, ignoring request: start...] ### Showing that systemd is
bailing out because of the chroot.
[...$ ps --no-headers -o comm 1
init...] ### showing the Chromebook is using init at PID 1
[...$ file /sbin/init
/sbin/init: symbolic link to /lib/systemd/systemd ...} ### showing that
init and systemd are linked in the chroot.
[...$ stat /sbin/init
File: /sbin/init -> /lib/systemd/systemd ...] ### Showing that systemd is
in use.
{...$ ls /usr/lib/systemd } ### Shows the systemd files are loaded.
[...$ systemctl is-active --quiet service
System has not been booted with systemd as init system (PID 1). Can't
operate.
Failed to connect to bus: Host is down ...] *### Systemd not active in
chroot*
*I'm wondering if adding a line in the rc would help complete the boot
process. *
Can you please help me troubleshoot this issue?
Thank you for your time.
yours truly,
Benjamin Godfrey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/2dd09d88/attachment-0001.htm>
------------------------------
Message: 3
Date: Wed, 26 Apr 2023 10:33:44 +0200
From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
To: Benjamin Godfrey <mr.benjamingodfrey@xxxxxxxxx>
Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: Completing the boot process for systemd
inside the chroot
Message-ID: <ZEjh6FduyO+JPRaf@gardel-login>
Content-Type: text/plain; charset=us-ascii
On Di, 25.04.23 13:26, Benjamin Godfrey (mr.benjamingodfrey@xxxxxxxxx) 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 classic chroot(). Use a
container manager for that, for example "systemd-nspawn -D
/some/directory -b"
Lennart
--
Lennart Poettering, Berlin
------------------------------
Subject: Digest Footer
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
------------------------------
End of systemd-devel Digest, Vol 156, Issue 26
**********************************************
