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

2023-12-29 Thread Salvatore Bonaccorso
Hi Herald, On Thu, Dec 28, 2023 at 05:17:48PM +0100, Harald Dunkel wrote: > On 2023-12-28 14:40:30, Salvatore Bonaccorso wrote: > > > > 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 .

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

2023-12-28 Thread Harald Dunkel
On 2023-12-28 14:40:30, Salvatore Bonaccorso wrote: 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 . Oh, I

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

2023-12-28 Thread Salvatore Bonaccorso
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

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

2023-12-28 Thread Harald Dunkel
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