My host is a fully up-to-date Questing, and freshly rebooted. Guests are Noble and Questing containers.
Which package do you think could have made a difference in your case? The latest rsyslog in Questing migrated over one month ago. -- You received this bug notification because you are a member of Debcrafters packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2123821 Title: bad restriction: apparmor="DENIED" [...] namespace="root//lxd-n_<var- snap-lxd-common-lxd>" profile="rsyslogd" name="/run/systemd/journal/dev-log" Status in apparmor package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Incomplete Bug description: On my Questing system running LXD containers, my kernel log is full of messages like: [ 129.551382] audit: type=1400 audit(1757925628.229:1005): apparmor="DENIED" operation="sendmsg" class="file" namespace="root//lxd-q_<var-snap-lxd-common-lxd>" profile="rsyslogd" name="/run/systemd/journal/dev-log" pid=5370 comm="systemd-journal" requested_mask="r" denied_mask="r" fsuid=1000000 ouid=1000000 One of my containers is named "q", hence the "root//lxd-q...". Some actual functionality is likely broken in the container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2123821/+subscriptions -- Mailing list: https://launchpad.net/~debcrafters-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~debcrafters-packages More help : https://help.launchpad.net/ListHelp
