Bug#978425: autopkgtest reboot functionality is broken with cgroupv2

2020-12-27 Thread Christian Brauner
On Sun, Dec 27, 2020 at 05:28:18PM +0100, Michael Biebl wrote: > Am 27.12.20 um 16:43 schrieb Christian Brauner: > > I'll give this a closer look. Is there any way I can tell autopkgtest to Ok, I think I fixed it: https://github.com/lxc/lxc/pull/3608 Can you please apply https://

Bug#978425: autopkgtest reboot functionality is broken with cgroupv2

2020-12-27 Thread Christian Brauner
On Sun, Dec 27, 2020 at 12:44:16PM +0100, Michael Biebl wrote: > Thanks for your quick reply, Christian. > > Am 27.12.20 um 12:31 schrieb Christian Brauner: > > Hm, I have two small fixes in > > https://github.com/lxc/lxc/pull/3608 > > prefixed with "cgroup2: "

Bug#978425: autopkgtest reboot functionality is broken with cgroupv2

2020-12-27 Thread Christian Brauner
On Sun, Dec 27, 2020 at 12:23:47PM +0100, Michael Biebl wrote: > Am 27.12.20 um 12:05 schrieb Christian Brauner: > > > $ sudo autopkgtest-build-lxc > > Sorry for the wrong instructions. This should have been: > $ sudo autopkgtest-build-lxc debian sid No problem at all;

Bug#978425: autopkgtest reboot functionality is broken with cgroupv2

2020-12-27 Thread Christian Brauner
On Sun, Dec 27, 2020 at 11:17:18AM +0100, Michael Biebl wrote: > Package: lxc > Version: 1:4.0.5-1 > Severity: important > User: pkg-systemd-maintain...@lists.alioth.debian.org > Usertags: cgroupv2 > X-Debbugs-Cc: Christian Brauner > > > Hi, > > since systemd 2

Bug#916639: LXC AppArmor confinement breaks systemd v240

2019-01-13 Thread Christian Brauner
02:00, intrigeri wrote: >Hi, > >Pierre-Elliott Bécue: >> Hi, > >> Le 11/01/2019 à 16:02, Christian Brauner a écrit : >>> Hm, unlikely. Can you carry a separate patch on top of 3.0.3 until >>> we release 3.0.4? > >> Sure, if it is applicable o

Bug#916639: LXC AppArmor confinement breaks systemd v240

2019-01-11 Thread Christian Brauner
On Fri, Jan 11, 2019 at 03:56:02PM +0100, Pierre-Elliott Bécue wrote: > Le 11/01/2019 à 15:01, Christian Brauner a écrit : > > On Fri, Jan 11, 2019 at 12:58:09AM +0100, Pierre-Elliott Bécue wrote: > >> Le dimanche 16 décembre 2018 à 20:22:05+0100, intrig...@debian.org a écrit  &g

Bug#916639: LXC AppArmor confinement breaks systemd v240

2019-01-11 Thread Christian Brauner
On Fri, Jan 11, 2019 at 12:58:09AM +0100, Pierre-Elliott Bécue wrote: > Le dimanche 16 décembre 2018 à 20:22:05+0100, intrig...@debian.org a écrit : > > Package: lxc > > Version: 1:3.0.3-1 > > Severity: normal > > Tags: patch > > X-Debbugs-Cc: Michael Biebl , Wolfgang Bumiller > > > > User: pkg-a

Bug#908223: Bug#908192

2018-10-23 Thread Christian Brauner
On Tue, Oct 23, 2018 at 11:54:08AM +0200, Pierre-Elliott Bécue wrote: > Le lundi 22 octobre 2018 à 16:39:12+0200, Christian Brauner a écrit : > > On Mon, Oct 22, 2018 at 02:29:19PM +0200, Pierre-Elliott Bécue wrote: > > > Cc-ing Christian as he proposed the patch. > > >

Bug#908223: Bug#908192

2018-10-22 Thread Christian Brauner
On Mon, Oct 22, 2018 at 02:29:19PM +0200, Pierre-Elliott Bécue wrote: > Cc-ing Christian as he proposed the patch. > > Le jeudi 18 octobre 2018 à 14:32:12+0200, Matthias Heinz a écrit : > > Hi, > > > > I've tried applying the patch to the 2.0.9 source. Unfortunately there have > > been more chan

Bug#908223: Bug#908192

2018-10-22 Thread Christian Brauner
return !(path->mnt->mnt_flags & MNT_NODEV) && !(path->mnt->mnt_sb->s_iflags & SB_I_NODEV); } which will cause an EPERM because the device node is located on an fs owned by non-init-userns and thus doesn't grant access to device nod

Bug#911509: Update to libcap2.26

2018-10-21 Thread Christian Brauner
Package: libcap2 Version: 1:2.25-1 Severity: normal Hey everyone, We recently pushed support for ambient capabilities and namespaces filesystem capabilities to libcap2 [1]. Together with Andrew Morgan, Serge Hallyn and I have released a version 2.26 of libcap2. Note that libcap2 has moved to a ne

Bug#908223: Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)

2018-10-14 Thread Christian Brauner
On Sat, Oct 13, 2018 at 10:26:57PM +0200, Salvatore Bonaccorso wrote: > control: 908192 blocked by 908223 > Control: tag 908192 + wontfix > > Hi Christian, > > On Tue, Oct 09, 2018 at 02:06:09AM +0200, Christian Brauner wrote: > > On Sat, 22 Sep 2018 21:20:19 +0

Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)

2018-10-08 Thread Christian Brauner
On Sat, 22 Sep 2018 21:20:19 +0200 Salvatore Bonaccorso wrote: > Hi, > > On Thu, Sep 20, 2018 at 06:09:07PM +0800, johnw wrote: > > > > Is it also reverted/back port to Debian? > > Because I still have this problem. > > it has not yet been reverted upstream, the discussion got stuck here: Hey, I'

Bug#812127: login: wrong German error message

2017-01-20 Thread Christian Brauner
So If I may weigh in as a native speaker. While "Arbeit ohne effektive root-Rechte keinesfalls möglich." as Helge suggested is possible it is still a little confusing. I'd simply use "Arbeit one effektive root-Recht nicht möglich." the sassy spirit of "cannot possibly work without" won't be cap

Bug#839843: /usr/bin/lxc-create: Ran rm -rf on an entire filesystem after failing to create a container

2016-10-28 Thread Christian Brauner
On Sat, Oct 29, 2016 at 12:38:40AM +0200, Christian Brauner wrote: > On Wed, 05 Oct 2016 13:25:18 -0400 Matthew Gabeler-Lee > wrote: > > Package: lxc > > Version: 1:2.0.4-1 > > Severity: normal > > File: /usr/bin/lxc-create > > > > I ran lxc-create to s

Bug#839843: /usr/bin/lxc-create: Ran rm -rf on an entire filesystem after failing to create a container

2016-10-28 Thread Christian Brauner
On Wed, 05 Oct 2016 13:25:18 -0400 Matthew Gabeler-Lee wrote: > Package: lxc > Version: 1:2.0.4-1 > Severity: normal > File: /usr/bin/lxc-create > > I ran lxc-create to setup an image, and realized I had given it the wrong > arguments (wrong distro version, nothing dramatic), so I stopped it with