Raised https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1188501
--
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/993706
Title:
Fix lxc-execute without rootfs failing apparmor
I guess given the release date that this fix is in Raring? Should I
raise a new bug since I'm getting a similar error in Raring?
--
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/993706
@Neil,
yes, please do raise a new bug.
--
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/993706
Title:
Fix lxc-execute without rootfs failing apparmor transitions
To manage
** Tags removed: needssru
--
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/993706
Title:
Fix lxc-execute without rootfs failing apparmor transitions
To manage notifications about this
This bug was fixed in the package lxc - 0.7.5-3ubuntu56
---
lxc (0.7.5-3ubuntu56) precise-proposed; urgency=low
* Fix Ubuntu template to install the host architecture of the required
mutli-arch packages (when using qemu-user-static) instead of hardcoded
amd64 version. (LP:
Marking verification-done based on above comment.
** Changed in: lxc (Ubuntu Precise)
Status: Fix Released = Fix Committed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Pleased to report that the fix to lxc reached us through our mirror
today (!) and that lxc-execute is working now. Nicely done.
AfC
** Changed in: lxc (Ubuntu Precise)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server
** Branch linked: lp:ubuntu/precise-proposed/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/993706
Title:
Fix lxc-execute without rootfs failing apparmor transitions
To manage
Hello Andrew, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
(The problem is actually that we need to make sure to mount our own
/proc, else, when using lxc.rootfs=/, we leave the host's /proc mounted,
and the apparmor library tries to set the lxc profile for the wrong
task)
--
You received this bug notification because you are a member of Ubuntu
Server
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu5
---
lxc (0.8.0~rc1-4ubuntu5) quantal; urgency=low
* 0082-umount-old-proc: fix proc auto-mount. If /proc is already mounted,
make sure that /proc/self points to 1, since we are container init.
Otherwise, assume proc
** Branch linked: lp:ubuntu/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/993706
Title:
Fix lxc-execute without rootfs failing apparmor transitions
To manage notifications about
** Description changed:
+ =
+ SRU Justification:
+ 1. impact: lxc-execute fails when apparmor transition is requested (as it is
by default)
+ 2. development fix: make sure the container's own proc is mounted before
attempting apparmor context transition
+ 3.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
14 matches
Mail list logo
