This bug was fixed in the package lxc - 2.0.0~rc5-0ubuntu1
---
lxc (2.0.0~rc5-0ubuntu1) xenial; urgency=medium
* New usptream release (2.0.0~rc5)
- Fix a number of cgfs issues (LP: #1549363, LP: #1543697, LP: #1552355)
- Fix attach failing to allocate a tty (LP: #1551960)
This bug was fixed in the package lxc - 2.0.0~rc5-0ubuntu1
---
lxc (2.0.0~rc5-0ubuntu1) xenial; urgency=medium
* New usptream release (2.0.0~rc5)
- Fix a number of cgfs issues (LP: #1549363, LP: #1543697, LP: #1552355)
- Fix attach failing to allocate a tty (LP: #1551960)
Unprivileged LXC still fails to start here...
kernel: 4.4.0-9.24
lxc: 2.0.0~rc4-0ubuntu1
$ lxc-start -d -n i386-trusty-gui
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in
foreground mode.
lxc-start:
Unprivileged LXC still fails to start here...
kernel: 4.4.0-9.24
lxc: 2.0.0~rc4-0ubuntu1
$ lxc-start -d -n i386-trusty-gui
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in
foreground mode.
lxc-start:
The containers now start after today's updates (2.0.0~rc4-0ubuntu1).
Also a new kernel was installed which may have fixed something too.
At any rate, looks like it's fixed for now.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The containers now start after today's updates (2.0.0~rc4-0ubuntu1).
Also a new kernel was installed which may have fixed something too.
At any rate, looks like it's fixed for now.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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/1549363
Title:
Unprivileged LXC will not start after today's updates
To
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549363
Title:
Unprivileged LXC will not start after today's updates
To manage
I updated to the latest LXC (2.0.0~rc3-0ubuntu2) and the cgroup
permission issue still occurs. The unprivileged containers are created
by the user and started by the user, ie, not root.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I updated to the latest LXC (2.0.0~rc3-0ubuntu2) and the cgroup
permission issue still occurs. The unprivileged containers are created
by the user and started by the user, ie, not root.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I have rebooted my machine multiple times and the issue(s) still occur.
--
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/1549363
Title:
Unprivileged LXC will not start after today's
I have rebooted my machine multiple times and the issue(s) still occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549363
Title:
Unprivileged LXC will not start after today's updates
To manage
That's very weird, all my xenial test systems show lxc-container-
default-cgns in the apparmor_status output
--
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/1549363
Title:
Unprivileged
That's very weird, all my xenial test systems show lxc-container-
default-cgns in the apparmor_status output
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549363
Title:
Unprivileged LXC will not
I grabbed 2.0.0~rc3-0ubuntu2 before I wrote those comments, as I noticed
the cgfs changes. My last reboot was this morning, between upgrading to
-0ubuntu1 and -0ubuntu2, so I think the apparmor stuff is still broken.
The profile doesn't even appear if I explicitly apparmor_parser -r, -a,
-R in any
I grabbed 2.0.0~rc3-0ubuntu2 before I wrote those comments, as I noticed
the cgfs changes. My last reboot was this morning, between upgrading to
-0ubuntu1 and -0ubuntu2, so I think the apparmor stuff is still broken.
The profile doesn't even appear if I explicitly apparmor_parser -r, -a,
-R in any
Hmm, does /etc/init.d/apparmor reload fix the profile not being loaded?
We've not been introducing new profiles very often and those profiles
are loaded through apparmor includes so I can certainly see a standard
dh_apparmor being confused by it and not reloading everything properly
on upgrade.
As for the cgroups, we've noticed at least one issue in the cgfs logic
of LXC which was fixed earlier today, the package is still going through
QA (currently in proposed), should make it to the release pocket within
a couple of hours.
The fix was specifically to fix unprivileged but root-owned
As for the cgroups, we've noticed at least one issue in the cgfs logic
of LXC which was fixed earlier today, the package is still going through
QA (currently in proposed), should make it to the release pocket within
a couple of hours.
The fix was specifically to fix unprivileged but root-owned
Hmm, does /etc/init.d/apparmor reload fix the profile not being loaded?
We've not been introducing new profiles very often and those profiles
are loaded through apparmor includes so I can certainly see a standard
dh_apparmor being confused by it and not reloading everything properly
on upgrade.
lxc-container-default-cgns doesn't show up in apparmor_status, despite
the other three being there.
If I hack a container's config to use lxc-container-default rather than
lxc-container-default-cgns, hack that profile to allow cgfs, and start
that container, lxc-container-default-cgns shows up
lxc-container-default-cgns doesn't show up in apparmor_status, despite
the other three being there.
If I hack a container's config to use lxc-container-default rather than
lxc-container-default-cgns, hack that profile to allow cgfs, and start
that container, lxc-container-default-cgns shows up
The cgroup errors go away if I manually create and chown a few parent
cgroups, but then the apparmor error returns.
--
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/1549363
Title:
The cgroup errors go away if I manually create and chown a few parent
cgroups, but then the apparmor error returns.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549363
Title:
Unprivileged LXC
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549363
Title:
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
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1549363
After the latest lxc updates (2.0.0~rc3-0ubuntu1), a new failure is now
occurring. See attached debug log.
** Attachment added: "start_lxc.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+attachment/4580930/+files/start_lxc.out
--
You received this bug notification because
After the latest lxc updates (2.0.0~rc3-0ubuntu1), a new failure is now
occurring. See attached debug log.
** Attachment added: "start_lxc.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+attachment/4580930/+files/start_lxc.out
--
You received this bug notification because
28 matches
Mail list logo
