[Bug 942325] [NEW] keep container from marking shared rootfs readonly on shutdown

[Serge Hallyn]

Public bug reported:

When a container shuts down, it tries to

   mount -o remount,ro /

If the container's '/' is a separate blockdev, that's fine.

If the container's '/' is on the host's rootfs, that's usually fine -
because something, somewhere, on the system will have a file open which
will make the readonly remount fail.

But if the container rootfs is a directory under
/var/lib/lxc/<container>/rootfs, and /var/lib/lxc is a separate
filesystem, and no other container is running, then that filesystem will
be marked readonly, causing future container starts or creations to
fail.

lxc-start needs to hold a file open for write for the duration of the
container's run.  '${rootfs}.hold' should be good.

** Affects: lxc (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/942325

Title:
  keep container from marking shared rootfs readonly on shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/942325/+subscriptions