Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #81343

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

Show all headers | View raw

Hi,

On Thu, Dec 28, 2023 at 02:13:28PM +0100, Harald Dunkel wrote:
> 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?

Because it needs backporting work in 6.1.y upstream, which for John
Johansen aimed to work on. You can read about the history and backlog
in #1050256 . So far I have not got a reply from John on
https://bugs.debian.org/1050256#215 .

Regards,
Salvatore

Back to linux.debian.kernel | Previous | Next — Previous in thread | 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