Some more information on cgroup-lite and where it may fail. - cgroup lite is triggered on "mounted MOUNTPOINT=/sys/fs/cgroup" => the path is shown as mountend above, so not it - The job then gets skipped if /bin/cgroups-mount doesn't exist => part of the cgroup-lite package, so not it - The job then gets skipped if /sys/fs/cgroup doesn't exist => was shown as mounted above, so not it - cgroup-lite exits if a cgroup entry is found in /etc/fstab - cgroup-lite exits if /proc/cgroups doesn't exist => all Ubuntu kernels have it, so not it
So the most likely reason I believe would be a "cgroup" entry of some sort in /etc/fstab, the second most likely reason would be a failure for the "mounted MOUNTPOINT=/sys/fs/cgroup" to be emitted by upstart somehow. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
