#1012459 systemd-logind fails on read-only filesystem

Package:
systemd
Source:
systemd
Description:
system and service manager
Submitter:
Date:
2022-06-09 21:39:09 UTC
Severity:
normal
#1012459#5
Date:
2022-06-07 17:41:47 UTC
From:
To:
Jun 07 19:12:22 localhost systemd[1]: Starting User Login Management...Jun 07 19:12:22 localhost systemd[401]: systemd-logind.service: Failed to set up special execution directory in /var/lib: Read-only file systemJun 07 19:12:22 localhost systemd[401]: systemd-logind.service: Failed at step STATE_DIRECTORY spawning /lib/systemd/systemd-logind: Read-only file systemJun 07 19:12:22 localhost systemd[1]: systemd-logind.service: Main process exited, code=exited, status=238/STATE_DIRECTORYJun 07 19:12:22 localhost systemd[1]: systemd-logind.service: Failed with result 'exit-code'.Jun 07 19:12:22 localhost systemd[1]: Failed to start User Login Management.Jun 07 19:12:22 localhost systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5.Jun 07 19:12:22 localhost systemd[1]: Stopped User Login Management.Jun 07 19:12:22 localhost systemd[1]: systemd-logind.service: Start request repeated too quickly.Jun 07 19:12:22 localhost systemd[1]: systemd-logind.service: Failed with result 'exit-code'.Jun 07 19:12:22 localhost systemd[1]: Failed to start User Login Management.

Debian GNU/Linux 11 Linux 5.10.0-13-amd64 Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux
#1012459#14
Date:
2022-06-09 21:35:38 UTC
From:
To:
You can make /usr ro without problems, but /tmp and /var (and /etc most
likely as well) need to be writable at the very least.

A fully ro system is simply not supported.