Description of problem: When running /usr/sbin/init in container, systemd-homed.service fails. Version-Release number of selected component (if applicable): systemd-245~rc1-3.fc33.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. podman run --rm -ti --systemd=true registry.fedoraproject.org/fedora:rawhide /usr/sbin/init Actual results: systemd v245~rc1-3.fc33 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=unified) Detected virtualization container-other. Detected architecture x86-64. Welcome to Fedora 33 (Container Image)! Set hostname to <522ca84a661f>. Initializing machine ID from random generator. initrd-root-fs.target: Requested dependency OnFailure=emergency.target ignored (target units cannot fail). /usr/lib/systemd/system/systemd-boot-system-token.service:21: Executable "bootctl" not found in path "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin" systemd-boot-system-token.service: Unit configuration has fatal error, unit will not be started. local-fs.target: Requested dependency OnFailure=emergency.target ignored (target units cannot fail). systemd-boot-system-token.service: Cannot add dependency job, ignoring: Unit systemd-boot-system-token.service has a bad unit file setting. [ OK ] Started Dispatch Password …ts to Console Directory Watch. [ OK ] Started Forward Password R…uests to Wall Directory Watch. [ OK ] Reached target Local File Systems. [ OK ] Reached target Paths. [ OK ] Reached target Remote File Systems. [ OK ] Reached target Slices. [ OK ] Reached target Swap. [ OK ] Listening on Process Core Dump Socket. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. [ OK ] Listening on User Database Manager Socket. ldconfig.service: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling. (This warning is only shown for the first unit using IP firewalling.) Starting Rebuild Dynamic Linker Cache... Starting Journal Service... Starting Create System Users... [ OK ] Started Create System Users. [ OK ] Started Rebuild Dynamic Linker Cache. [ OK ] Started Journal Service. Starting Flush Journal to Persistent Storage... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started Create Volatile Files and Directories. Starting Rebuild Journal Catalog... Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Rebuild Journal Catalog. Starting Update is Completed... [ OK ] Started Update is Completed. [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting Home Manager... Starting Permit User Sessions... [FAILED] Failed to start Home Manager. See 'systemctl status systemd-homed.service' for details. [ OK ] Started Permit User Sessions. [ OK ] Reached target Multi-User System. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Expected results: With Fedora 31 container, I see systemd v243.7-1.fc31 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=unified) Detected virtualization container-other. Detected architecture x86-64. Welcome to Fedora 31 (Container Image)! Set hostname to <4b20d8f80ff8>. Initializing machine ID from random generator. [ OK ] Started Dispatch Password …ts to Console Directory Watch. [ OK ] Started Forward Password R…uests to Wall Directory Watch. [ OK ] Reached target Local File Systems. [ OK ] Reached target Paths. [ OK ] Reached target Remote File Systems. [ OK ] Reached target Slices. [ OK ] Reached target Swap. [ OK ] Listening on Process Core Dump Socket. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. ldconfig.service: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling. (This warning is only shown for the first unit using IP firewalling.) Starting Rebuild Dynamic Linker Cache... Starting Journal Service... Starting Create System Users... [ OK ] Started Create System Users. [ OK ] Started Rebuild Dynamic Linker Cache. [ OK ] Started Journal Service. Starting Flush Journal to Persistent Storage... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started Create Volatile Files and Directories. Starting Rebuild Journal Catalog... Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Rebuild Journal Catalog. Starting Update is Completed... [ OK ] Started Update is Completed. [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting Permit User Sessions... [ OK ] Started Permit User Sessions. [ OK ] Reached target Multi-User System. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Additional info: The systemd-boot-system-token.service issue was filed as bug 1807462. Maybe systemd-homed.service shouldn't be started at all in containers by default since there rarely are regular (human) users there.
https://github.com/systemd/systemd/pull/14970
Fixed in rawhide now.
FEDORA-2020-645de57f2e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-645de57f2e
systemd-245.2-1.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-645de57f2e
I confirm the fix is in registry.fedoraproject.org/fedora:32 now with systemd-245~rc1-3.fc32.x86_64.
FEDORA-2020-645de57f2e has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
For some reason, bodhi didn't close this bug.