why do I have to use backports kernel to make LXC work on Bookworm?

From	Harald Dunkel <harri@afaics.de>
Newsgroups	linux.debian.kernel
Subject	why do I have to use backports kernel to make LXC work on Bookworm?
Date	2023-12-28 14:30 +0100
Message-ID	<HPYCt-gGII-1@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi folks,

apparently LXC is affected by a bug around apparmor support for months,
see #1052934 and #1050256. The workaround is to set PrivateNetwork=false
(set by default as a security measure) or to use a backports kernel.

AFAIU reason is a bug in 6.1. The fix (1cf26c3d2c4c) is not a one-liner,
but reasonably small, and it has already been verified, so how comes it
is still in the loop for weeks?


Regards

Harri

Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

why do I have to use backports kernel to make LXC work on Bookworm? Harald Dunkel <harri@afaics.de> - 2023-12-28 14:30 +0100
  Re: why do I have to use backports kernel to make LXC work on  Bookworm? Salvatore Bonaccorso <carnil@debian.org> - 2023-12-28 14:50 +0100
    Re: why do I have to use backports kernel to make LXC work on  Bookworm? Harald Dunkel <harri@afaics.de> - 2023-12-28 17:20 +0100
      Re: why do I have to use backports kernel to make LXC work on  Bookworm? Salvatore Bonaccorso <carnil@debian.org> - 2023-12-29 13:50 +0100

csiph-web