[Bug 1514690] Re: rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group

[Serge Hallyn]

With cgfs i actually wasn't able to start the container in the first
place.  I've now fixed at least that.

it wasn't the mkdir which was failing, but the subsequent attempt to
attach itself to it.  That's because while cgmanager used to chown the
child files after creating a directory for us, cgfs wasn't doing that.

Now I'm at least at the point you were at - i can boot, but reboot
hangs, almost the same way:

Failed to create /lxc/x1/init.scope control group: No such file or directory
Failed to allocate manager object: No such file or directory
[!!!!!!] Failed to allocate manager object, freezing.

Note the error is not ENOENT.  When I check the rootfs after the fact,
there is no init.scope directory...

Debug statement in lxcfs suggests that no mkdir was ever called.

-- 
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/1514690

Title:
  rebooting container with systemd >= 226 fails to create /lxc/adt-
  xenial/init.scope control group

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