Description of problem:

When systemd container is run as read-only, the state of systemd is shows as degraded, presumably because systemd-update-utmp.service failed.

Version-Release number of selected component (if applicable):

REPOSITORY                          TAG   IMAGE ID       CREATED       SIZE
registry.fedoraproject.org/fedora   28    ded494ce3076   7 weeks ago   264MB

How reproducible:

Deterministic.

Steps to Reproduce:
1. sudo podman run --read-only --name systemd -d registry.fedoraproject.org/fedora:28 /usr/sbin/init
2. sudo podman exec systemd systemctl is-system-running
3. sudo podman exec systemd systemctl status systemd-update-utmp.service

Actual results:

degraded
exit status 1

● systemd-update-utmp.service - Update UTMP about System Boot/Shutdown
   Loaded: loaded (/usr/lib/systemd/system/systemd-update-utmp.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2018-11-30 12:15:49 UTC; 2min 45s ago
     Docs: man:systemd-update-utmp.service(8)
           man:utmp(5)
  Process: 20 ExecStart=/usr/lib/systemd/systemd-update-utmp reboot (code=exited, status=1/FAILURE)
 Main PID: 20 (code=exited, status=1/FAILURE)

Nov 30 12:15:49 daba0cea4007 systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Nov 30 12:15:49 daba0cea4007 systemd[1]: systemd-update-utmp.service: Main process exited, code=exited, status=1/FAILURE
Nov 30 12:15:49 daba0cea4007 systemd[1]: systemd-update-utmp.service: Failed with result 'exit-code'.
Nov 30 12:15:49 daba0cea4007 systemd[1]: Failed to start Update UTMP about System Boot/Shutdown.
exit status 3

Expected results:

running

The systemd-update-utmp.service should either be loaded/active, or it should not be running in read-only container at all, based on some condition.

Additional info: