Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #59355
| From | intrigeri <intrigeri@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#880502: [pkg-apparmor] Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10 |
| Date | 2017-11-05 13:20 +0100 |
| Message-ID | <uIrUt-4X8-3@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <uH1po-XL-19@gated-at.bofh.it> <uHnpT-7o1-1@gated-at.bofh.it> <uHpi2-8vl-3@gated-at.bofh.it> <uH1po-XL-19@gated-at.bofh.it> <uHpi2-8vl-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Hi, Antonio Terceiro: > The workaround that works is using the setting in the container > configuration: > lxc.aa_profile = unconfined > with disables apparmor entirely. > I have just uploaded lxc 1:2.0.9-4 setting this for all containers. This > is not the greatest solution, but it's also not worse than the state of > affairs before apparmor was enabled by default in the Debian kernel: it > was already not possible to use lxc with apparmor in Debian. Fully agreed: top priority is to ensure AppArmor doesn't break things, so let's disable any profile that is not ready for prime time. Adding AppArmor confinement where we had none previously can come later. Cheers, -- intrigeri
Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#880502: lxc: cannot start container (kernel related?) Antonio Terceiro <terceiro@debian.org> - 2017-11-01 14:40 +0100
Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10 Evgeni Golov <evgeni@debian.org> - 2017-11-01 15:50 +0100
Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10 Ben Hutchings <ben@decadent.org.uk> - 2017-11-01 22:20 +0100
Bug#880502: [pkg-apparmor] Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10 Christian Boltz <debian-bugs@cboltz.de> - 2017-11-02 19:30 +0100
Bug#880502: lxc: cannot start container with kernel 4.13.10 Evgeni Golov <evgeni@debian.org> - 2017-11-02 20:20 +0100
Bug#880502: [pkg-apparmor] Bug#880502: lxc: cannot start container with kernel 4.13.10 Felix Geyer <fgeyer@debian.org> - 2017-11-03 19:40 +0100
Bug#880502: [pkg-apparmor] Bug#880502: lxc: cannot start container with kernel 4.13.10 intrigeri <intrigeri@debian.org> - 2017-11-05 13:30 +0100
Bug#880502: [pkg-apparmor] Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10 intrigeri <intrigeri@debian.org> - 2017-11-05 13:20 +0100
csiph-web