Systemd-logind.service failed to start in nested unprivileged container


I have created a nested container in an unprivileged container. Both are Ubuntu 18.04.

In the nested container, I found that the systemd-logind.service failed to start during startup. When I run “systemctl list-jobs”, there are many other systemd services waiting for the systemd-logind.service to start.

In /var/log/syslog and journalctl -u systemd-logind.service, the error messages are:

Starting Login Service…
systemd-logind.service: Start operation timed out. Terminating
systemd-logind.service: Failed with result ‘timeout’
Failed to start Login Service

There is no such problem when I launch the container in a physical host.

Is there any configuration I need to use to solve this problem?