Your message dated Mon, 5 Dec 2022 22:32:04 +0100
with message-id <[email protected]>
and subject line Re: Bug#1019147: [systemd-devel] systemd-container: Trying to
use a bookworm chroot with a buster host fails / Failed to create /init.scope
control group
has caused the Debian Bug report #1019147,
regarding systemd-container: Trying to use a bookworm chroot with a buster host
fails / Failed to create /init.scope control group
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1019147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019147
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd-container
Severity: wishlist
X-Debbugs-Cc: [email protected]
Dear Maintainer,
I tried to run on top of a buster system
with systemd-container 241-7~deb10u8 to start a container
with a current bookworm chroot with systemd-container 251.4-3.
This buster system was running linux-image 4.19.0-21-amd64.
This failed with following error:
root@debian:~# systemd-nspawn --directory=/var/lib/machines/test-bookworm
--boot --network-veth
Spawning container test-bookworm on /var/lib/machines/test-bookworm.
Press ^] three times within 1s to kill container.
systemd 251.4-3 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA
+SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2
+IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT
-QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP
+SYSVINIT default-hierarchy=unified)
Detected virtualization systemd-nspawn.
Detected architecture x86-64.
Welcome to Debian GNU/Linux bookworm/sid!
Hostname set to <debian>.
Failed to create /init.scope control group: Operation not permitted
Failed to allocate manager object: Operation not permitted
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...
Container test-bookworm failed with error code 255.
So this report is mostly to ask if this expected or desired to work?
I omitted the version number as I don't know if this should be tracked
with the buster or the bookworm version.
Kind regards,
Bernhard
-- System Information:
Debian Release: 10.12
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500,
'oldstable-proposed-updates-debug'), (500, 'oldstable-debug'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-21-amd64 (SMP w/16 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd-container depends on:
ii dbus 1.12.20-0+deb10u1
ii libacl1 2.2.53-4
ii libbz2-1.0 1.0.6-9.2~deb10u1
ii libc6 2.28-10+deb10u1
ii libcurl3-gnutls 7.64.0-4+deb10u3
ii libgcrypt20 1.8.4-5+deb10u1
ii liblzma5 5.2.4-1+deb10u1
ii libseccomp2 2.3.3-4
ii libselinux1 2.8-1+b1
ii systemd 241-7~deb10u8
ii zlib1g 1:1.2.11.dfsg-1+deb10u1
Versions of packages systemd-container recommends:
ii btrfs-progs 4.20.1-2
ii libnss-mymachines 241-7~deb10u8
--- End Message ---
--- Begin Message ---
Am 05.12.22 um 22:10 schrieb Michael Biebl:
Hi Bernhard
Am 05.12.22 um 18:31 schrieb Bernhard Übelacker:
Thanks for the update!
I guess this means we can close the bug report?
Regards,
Michael
Hello Michel,
yes, I am trying to close it.
Thanks for your time.
Kind regards,
Bernhard
--- End Message ---
