Adding qemu-linaro (for qemu-user-static) as per irc conversation in
#ubuntu-devel.
Suggestion is to have qemu-user-static.postinst not install any targets
matching `uname -m` or current userspace.
** Also affects: qemu-linaro (Ubuntu)
Importance: Undecided
Status: New
--
You
** Changed in: linux (Ubuntu)
Status: Invalid = 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/917660
Title:
Installing qemu-user-static in an i386 lxc container
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
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/917660
Title:
Installing qemu-user-static in an i386 lxc container
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: binfmt-support (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.
** Changed in: lxc (Ubuntu)
Status: Confirmed = Fix Released
--
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/917660
Title:
Installing qemu-user-static in an i386 lxc container
The fix to bug 947617 seems to have caused a regression here; reopening.
** Changed in: lxc (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
It's indeed fixed, thanks!
--
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/917660
Title:
Installing qemu-user-static in an i386 lxc container applies the
binfmt changes to the host,
Although I now get an error when uninstalling qemu-user-static. I don't
worry about that because I know what's going on, but I thought I'd
mention anyway
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
This should be fixed in lxc in precise, where the apparmor policy should
prevent it from happening.
I've marked the kernel bug invalid, but kept the binfmt-support bug new.
If there is something which that package could do to help the general
(non-lxc) case, that'd be terrific. I'm not sure
** Tags removed: kernel-request-3.2.0-10.17 kernel-request-3.2.0-10.18
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
@serge -- if this is going to be fixed using an apparmour policy should
we be flipping the kernel task over to apparmor ?
--
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/917660
Title:
@Andy -- that depends on whether we consider the kernel part of this a
bug or not.
For lxc it'll be fixed with an apparmor policy shipped with lxc.
For update-binfmts more generally, there might be way for that program
to be smarter.
But still the kernel itself is reading over proc and/or sys
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
I reproduce it yesterday by creating a fresh precise-i386 container on
my precise-amd64 host and installing qemu-user-static in it. This is how
I created it:
lxc-create -n $CONTAINER_NAME -t ubuntu -f /tmp/network.conf -- -r
precise -a i386
--
You received this bug notification because you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Problem still exists on latest kernel
status confirmed
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8dUNMACgkQ8F5AvJx1xKYptACglD1Mt1bVgKD7al5UlpdVgvlF
Thanks, Guilherme. I'm sorry, should have mentioned that no, a new
kernel was not expected to fix that.
For lxc containers, we can (and should) fix this using an apparmor
policy.
I don't know if there is a reasonable way that update-binfmts itself can
detect this. I'll mark this as affecting
When I tried to reproduce this, I failed. It appeared to be due to the
container not having /lib/modules.
--
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/917660
Title:
Installing
Is the new kernel still on -proposed or has it been accepted already? I
just ran apt-get update/upgrade and didn't get that.
Also, is it really worth testing this on the new kernel?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/917660
Title:
Installing qemu-user-static in an i386 lxc
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
--
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/917660
Title:
21 matches
Mail list logo
