Some context: This was motivated on real hardware, not containers. For
"full" installations like VMs or real-iron the initrd already mounts
/run, and if it is already mounted then systemd won't touch it. As there
is no initrd in containers,
https://github.com/systemd/systemd/blob/master/src/core/mount-setup.c
will kick in and mount early stuff like /run, /proc/, etc. We can't
influence mounts from mount-setup.c with fstab as this happens (and
needs to happen) before /etc/fstab even gets parsed. But we could either
make initramfs-tools look at fstab and mount /run differently
(preferred), or remount /run etc. later in the game (that sounds racy,
inelegant, and might fail if you have options which can't be applied on
remount; I don't like that very much).
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540803
Title:
systemd doesn't respect /etc/fstab for internal mounts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1540803/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
