-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Description
systemd version the issue has been seen with
It's complicated. I am using systemd 241 on my main system, but am using the latest compiled systemd-nspawn binary. (247)
Used distribution
Host system: ARMhf Debian 10
I have downloaded an armhf Ubuntu 20.04 image. After mounting the image to /media/pi/vdesktop
, I run this command:
sudo systemd-nspawn -bD /media/pi/vdesktop
Full output:
Spawning container vdesktop on /media/pi/vdesktop.
Press ^] three times within 1s to kill container.
Host and machine ids are equal (d1dc3b5f97b7a536cd51a46a5faa0e3c): refusing to link journals
systemd 245.4-4ubuntu3.2 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
Detected virtualization systemd-nspawn.
Detected architecture arm64.
Welcome to Ubuntu 20.04.1 LTS!
Set hostname to <ubuntu>.
/lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
[ OK ] Reached target Slices.
[ OK ] Reached target Swap.
[ OK ] Listening on initctl Compatibility Named Pipe.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket.
Starting Journal Service...
Starting Set the console keyboard layout...
Mounting FUSE Control File System...
Starting Remount Root and Kernel File Systems...
[ OK ] Started Journal Service.
[ OK ] Finished Set the console keyboard layout.
[ OK ] Mounted FUSE Control File System.
[FAILED] Failed to start Remount Root and Kernel File Systems.
See 'systemctl status systemd-remount-fs.service' for details.
Starting Flush Journal to Persistent Storage...
Starting Create System Users...
[ OK ] Finished Create System Users.
Starting Create Static Device Nodes in /dev...
[ OK ] Finished Flush Journal to Persistent Storage.
[ OK ] Finished Create Static Device Nodes in /dev.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Commit a transient machine-id on disk...
Starting Create Volatile Files and Directories...
[ OK ] Started Dispatch Password …ts to Console Directory Watch.
[ OK ] Reached target Local Encrypted Volumes.
[ OK ] Finished Tell Plymouth To Write Out Runtime Data.
[FAILED] Failed to start Commit a transient machine-id on disk.
See 'systemctl status systemd-machine-id-commit.service' for details.
[ OK ] Finished Create Volatile Files and Directories.
Starting Network Name Resolution...
[ OK ] Reached target System Time Set.
[ OK ] Reached target System Time Synchronized.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Finished Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Started Trigger anacron every hour.
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Periodic ext4 Onli…ata Check for All Filesystems.
[ OK ] Started Refresh fwupd metadata regularly.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Message of the Day.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Paths.
[ OK ] Reached target Timers.
[ OK ] Listening on Unix socket for apport crash forwarding.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on CUPS Scheduler.
[ OK ] Listening on D-Bus System Message Bus Socket.
Starting Socket activation for snappy daemon.
[ OK ] Listening on UUID daemon activation socket.
[ OK ] Listening on Socket activation for snappy daemon.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting LSB: network connection manager...
Starting Permit User Sessions...
Starting Rotate log files...
Starting Daily man-db regeneration...
[ OK ] Finished Permit User Sessions.
[ OK ] Started LSB: network connection manager.
[ OK ] Reached target OEM Configuration.
[ OK ] Started D-Bus System Message Bus.
Starting Network Manager Script Dispatcher Service...
[ OK ] Started Network Manager Script Dispatcher Service.
Starting WPA supplicant...
[ OK ] Started WPA supplicant.
[ OK ] Finished Daily man-db regeneration.
[ OK ] Finished Rotate log files.
[ OK ] Started Network Name Resolution.
[ OK ] Reached target Network.
[ OK ] Reached target Host and Network Name Lookups.
Linux kernel version used (uname -a
)
Linux raspberrypi 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l GNU/Linux
Expected behaviour you didn't see
I expected the boot process to finish successfully. I expected to be able to login.
Unexpected behaviour you saw
Instead, it gets stuck at
[ OK ] Reached target Host and Network Name Lookups.
in the boot process. It's stuck there forever and never proceeds further.
How to fix? Is there a systemd service I can mask in the Ubuntu image to allow the boot process to continue?