[yocto] read-only-rootfs causes systemd-tmpfiles-setup.service failure ( symlink(../run/lock, /var/lock) failed: Read-only file system)

[richard_allen at keysight.com]

I am build an image with read-only-rootfs
When enabled, during startup I get a 

[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.



● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor pre
set: enabled)
   Active: failed (Result: exit-code) since Fri 2017-09-01 19:16:27 UTC; 3min 52s ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 945 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=
/dev (code=exited, status=1/FAILURE)
 Main PID: 945 (code=exited, status=1/FAILURE)

Sep 01 19:16:27 dso systemd[1]: Starting Create Volatile Files and Directories...
Sep 01 19:16:27 dso systemd-tmpfiles[945]: symlink(../run/lock, /var/lock) failed: Read-only file system
Sep 01 19:16:27 dso systemd-tmpfiles[945]: "/var/tmp" already exists and is not a directory.
Sep 01 19:16:27 dso systemd-tmpfiles[945]: "/var/log" already exists and is not a directory.
Sep 01 19:16:27 dso systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
Sep 01 19:16:27 dso systemd[1]: Failed to start Create Volatile Files and Directories.
Sep 01 19:16:27 dso systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
Sep 01 19:16:27 dso systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.


Not clear if I should be worried about this.
If so, what should be done?
Thanks


Richard C. Allen
Keysight Technologies
richard_allen at Keysight.com