Serge is out today actually, I'll try to take a look.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1559169
Title:
containers no longer start after upgrade to
Curtis: can you paste a log to confirm it's the same issue as Colin?
It looks like some of the cgroup:mixed logic recently introduced in
cgfsng (to match that of the old cgfs backend) is a bit wrong here and
attempts to create a cpu/cpuset,cpuacct symlink instead of symlinking
cpu to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Ok, cool, that confirms it's the same thing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1559169
Title:
containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1559169
Title:
containers no longer start after upgrade to
This was also seen by the in Juju CI on the wily hosts that pull lxd/lxc
packages from the lxd ppa. We downgrades the wily machines to packages
from wily-updates to get lxc working again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This is the error
jenkins@wily-slave:~$ sudo lxc-start -n curtis -F
ln: failed to create symbolic link
‘/usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup/cpu/cpu,cpuacct’: Read-only file
system
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: conf.c: lxc_setup: 3750 failed to
7 matches
Mail list logo
