/tmp is only guaranteed to be in a usable state after sysinit.target
currently. Or more generally, after system is fully up only.
During boot (initramfs, post-initramfs, early boot, post-boot) system
services should use /run, private runtime dir, private tmp dir.
This is not a bug in Ubuntu boot sequence. Please fix cloud-init to use
/run.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1707222
Title:
usage of /tmp during boot is not safe due to systemd-tmpfiles-clean
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1707222/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
