Bug#1098521: apparmor 4.x breaks systemd user namespacing in lxc containers

2025-03-17 Thread Mathias Gibbens
In my testing I needed to make one additional change to the base lxc apparmor profile, and I've replied to the upstream bug report asking for feedback, since I'm not an apparmor expert. Once I get an ACK on that I'll update the lxc package for Debian. Mathias signature.asc Description: This is

Bug#1098521: apparmor 4.x breaks systemd user namespacing in lxc containers

2025-03-15 Thread Jing Luo
Control: severity -1 serious Control: found -1 1:6.0.3-1 Hi! IMO this is an RC bug, but the fix is easy. In [1] upstream doesn't seem to be willing to fix this, because it would break users of other distros that use older apparmor, so maybe it's best for debian to use the ubuntu patch [2] bef

Bug#1098521: [pkg-apparmor] Bug#1098521: apparmor 4.x breaks systemd user namespacing in lxc containers

2025-03-03 Thread intrigeri
Control: reassign -1 lxc Hi, Antoine Le Gonidec (2025-02-21): > When upgrading apparmor (and libapparmor1) to 4.1.0~beta5-2, multiple > services spawned by systemd in lxc containers fail to start, with denied > permissions errors. > > Errors similar to the following ones can be found in the kerne

Bug#1098521: apparmor 4.x breaks systemd user namespacing in lxc containers

2025-02-21 Thread Antoine Le Gonidec
Package: apparmor Version: 4.1.0~beta5-2 Severity: important When upgrading apparmor (and libapparmor1) to 4.1.0~beta5-2, multiple services spawned by systemd in lxc containers fail to start, with denied permissions errors. Errors similar to the following ones can be found in the kernel logs: ap