Thanks for reporting this bug.
This is another side effect stemming from the fact that the kernel
doesn't provide a good way to detect poweroff.vs.reboot in containers
yet. The workaround is for the container parent to watch the
container's /var/run/utmp. As a result of that, we can't let the
container mount tmpfs on /var/run, because then the utmp used by the
container would be hidden from the parent. As a result of that,
/etc/init/mounted-varrun.conf does not run, and that is where
/var/run/lock is created.
This should be fixed in lxcguest.conf, which does the other ugly manual
recreation of things we want in {/var}/run.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880030
Title:
oneiric container problem: missing /run/lock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/880030/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
