[Bug 2029299] [NEW] armhf lxc container in mantic does not start

Vladimir Petko 2029299 at bugs.launchpad.net
Tue Aug 1 20:14:12 UTC 2023


Public bug reported:

1. Create a privileged container:
----------------------
$ sudo lxc-create -t ubuntu --name armhf2 -- -a armhf -r mantic
Checking cache download in /var/cache/lxc/mantic/rootfs-armhf ... 
Copy /var/cache/lxc/mantic/rootfs-armhf to /var/lib/lxc/armhf2/rootfs ... 
Copying rootfs to /var/lib/lxc/armhf2/rootfs ...
Generating locales (this might take a while)...
  en_US.UTF-8... done
Generation complete.
Creating SSH2 RSA key; this may take some time ...
3072 SHA256:Jrw9h/HuVeKRJTnzsHh1VaM6i9vx7o3Bt5ZLJ43ZLNA root at bsp (RSA)
Creating SSH2 ECDSA key; this may take some time ...
256 SHA256:B63SaoqMi1xkoSzdFwIDs5Q/vR5wnRBYzviJgvkHsj8 root at bsp (ECDSA)
Creating SSH2 ED25519 key; this may take some time ...
256 SHA256:p4ikVcAA5zE7Y5X5lm4UDaKi4radncqKdgfTVQd8siQ root at bsp (ED25519)
/proc/ is not mounted, but required for successful operation of systemd-tmpfiles. Please mount /proc/. Alternatively, consider using the --root= or --image= switches.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.

Current default time zone: 'Etc/UTC'
Local time is now:      Tue Aug  1 20:00:52 UTC 2023.
Universal Time is now:  Tue Aug  1 20:00:52 UTC 2023.


##
# The default user is 'ubuntu' with password 'ubuntu'!
# Use the 'sudo' command to run tasks as root in the container.
##

------------------------------

2. start the container,  attach to it and upgrade( see upgrade.log)

3. container no longer starts
-------------
bsp at bsp:~$ sudo lxc-start -F armhf2
systemd 253.5-1ubuntu1 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 lxc.
Detected architecture arm.

Welcome to Ubuntu Mantic Minotaur (development branch)!

Failed to fork off sandboxing environment for executing generators: Protocol error
[!!!!!!] Failed to start up manager.
---------------

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2029299

Title:
  armhf lxc container in mantic does not start

Status in systemd package in Ubuntu:
  New

Bug description:
  1. Create a privileged container:
  ----------------------
  $ sudo lxc-create -t ubuntu --name armhf2 -- -a armhf -r mantic
  Checking cache download in /var/cache/lxc/mantic/rootfs-armhf ... 
  Copy /var/cache/lxc/mantic/rootfs-armhf to /var/lib/lxc/armhf2/rootfs ... 
  Copying rootfs to /var/lib/lxc/armhf2/rootfs ...
  Generating locales (this might take a while)...
    en_US.UTF-8... done
  Generation complete.
  Creating SSH2 RSA key; this may take some time ...
  3072 SHA256:Jrw9h/HuVeKRJTnzsHh1VaM6i9vx7o3Bt5ZLJ43ZLNA root at bsp (RSA)
  Creating SSH2 ECDSA key; this may take some time ...
  256 SHA256:B63SaoqMi1xkoSzdFwIDs5Q/vR5wnRBYzviJgvkHsj8 root at bsp (ECDSA)
  Creating SSH2 ED25519 key; this may take some time ...
  256 SHA256:p4ikVcAA5zE7Y5X5lm4UDaKi4radncqKdgfTVQd8siQ root at bsp (ED25519)
  /proc/ is not mounted, but required for successful operation of systemd-tmpfiles. Please mount /proc/. Alternatively, consider using the --root= or --image= switches.
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.

  Current default time zone: 'Etc/UTC'
  Local time is now:      Tue Aug  1 20:00:52 UTC 2023.
  Universal Time is now:  Tue Aug  1 20:00:52 UTC 2023.

  
  ##
  # The default user is 'ubuntu' with password 'ubuntu'!
  # Use the 'sudo' command to run tasks as root in the container.
  ##

  ------------------------------

  2. start the container,  attach to it and upgrade( see upgrade.log)

  3. container no longer starts
  -------------
  bsp at bsp:~$ sudo lxc-start -F armhf2
  systemd 253.5-1ubuntu1 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 lxc.
  Detected architecture arm.

  Welcome to Ubuntu Mantic Minotaur (development branch)!

  Failed to fork off sandboxing environment for executing generators: Protocol error
  [!!!!!!] Failed to start up manager.
  ---------------

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2029299/+subscriptions




More information about the foundations-bugs mailing list