Yes, I think that is the bug. Here is the output:
$ cat /proc/self/cgroup
10:cpuset:/user.slice
9:blkio:/user.slice
8:cpu,cpuacct:/user.slice
7:perf_event:/user.slice
6:devices:/user.slice
5:freezer:/user.slice
4:memory:/user.slice
3:net_cls,net_prio:/user.slice
2:hugetlb:/user.slice
I assume this is due to bug 1470060. Could you please show
/proc/self/cgroup to confirm?
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server
I'm also attaching the log during the failure.
** Attachment added: start.out
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470135/+attachment/4422483/+files/start.out
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Also of note, there was an update to systemd today, which tends to cause
issues with lxc:(
--
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/1470135
Title:
Wily lxc will not start on Wily
*** This bug is a duplicate of bug 1470060 ***
https://bugs.launchpad.net/bugs/1470060
** This bug has been marked a duplicate of bug 1470060
[wily] unprivileged containers don't work any more due to missing cgroup
permissions
--
You received this bug notification because you are a
