Bug#880502: [pkg-apparmor] Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10

Path	csiph.com!feeder.erje.net!2.eu.feeder.erje.net!newsfeed.datemas.de!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
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	Sun, 05 Nov 2017 13:20:01 +0100
Message-ID	<uIrUt-4X8-3@gated-at.bofh.it> (permalink)
References	<uH1po-XL-19@gated-at.bofh.it> <uH1po-XL-19@gated-at.bofh.it> <uH1Sq-1og-1@gated-at.bofh.it> <uH1po-XL-19@gated-at.bofh.it> <uH2v8-1Fb-5@gated-at.bofh.it> <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>
X-Mailbox-Line	From debian-bugs-dist-request@lists.debian.org Sun Nov 5 12:12:10 2017
Old-Return-Path	<debbugs@buxtehude.debian.org>
X-Spam-Flag	NO
X-Spam-Score	-4.2
Reply-To	intrigeri <intrigeri@debian.org>, 880502@bugs.debian.org
Resent-To	debian-bugs-dist@lists.debian.org
Resent-Cc	pkg-lxc <pkg-lxc-devel@lists.alioth.debian.org>
X-Debian-Pr-Message	followup 880502
X-Debian-Pr-Package	lxc
X-Debian-Pr-Source	lxc
X-Spam-Bayes	score:0.0000 Tokens: new, 7; hammy, 113; neutral, 41; spammy, 1. spammytokens:0.920-+--greatest hammytokens:0.000-+--Hi:message, 0.000-+--Hi:0200, 0.000-+--HRU:boum.org, 0.000-+--HF:Uintrigeri, 0.000-+--Hrp:U*intrigeri
MIME-Version	1.0
Content-Type	text/plain
X-Debian-Message	from BTS
X-Mailing-List	<debian-bugs-dist@lists.debian.org> archive/latest/1416711
List-ID	<debian-bugs-dist.lists.debian.org>
List-URL	<https://lists.debian.org/debian-bugs-dist/>
Approved	robomod@news.nic.it
Lines	24
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Cc	Evgeni Golov <evgeni@debian.org>, 880502@bugs.debian.org, pkg-apparmor-team@lists.alioth.debian.org, debian-kernel@lists.debian.org
X-Original-Date	Sun, 05 Nov 2017 13:09:10 +0100
X-Original-Message-ID	<85a801x6zd.fsf@boum.org>
X-Original-References	<20171101133231.bjcvcpayaezafxvp@debian.org> <20171101133231.bjcvcpayaezafxvp@debian.org> <20171101140012.m5amxxdl72cgdh6u@debian.org> <20171101133231.bjcvcpayaezafxvp@debian.org> <20171101143823.m3ro65t7rimbmfl3@nana.phantasia.die-welt.net> <20171101133231.bjcvcpayaezafxvp@debian.org> <20171102130410.rxsdyfv5nhrpbchi@debian.org> <20171102150657.d5tv4ysh2tfattfp@debian.org> <20171101133231.bjcvcpayaezafxvp@debian.org> <20171102150657.d5tv4ysh2tfattfp@debian.org>
Xref	csiph.com linux.debian.bugs.dist:861045 linux.debian.kernel:59355

Cross-posted to 2 groups.

Show key headers only | View raw

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

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