So far that does seem to confirm the hypothesis that since the phone has systemd installed (but unused), this meets lxc's dependency on systemd | cgroup-lite but as upstart is used to boot and upstart itself doesn't mount the cgroup controllers, this results in a system without cgroups mounted.
Having whatever package sets up the android container depend directly on cgroup-lite would fix that dependency issue, though from the logs provided so far, it looks like cgroup-lite is either not starting or is failing. I'm keeping the LXC task open for now, but there's so far been no indication of an actual bug in LXC or in its packaging, instead the phone seed is doing something that's not seen anywhere else (depend on systemd but not use it) which we can't do anything about from a packaging point of view. The rest of the issue appears to be some bad interaction between cgroup-lite and the init configuration on the Ubuntu phone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
