Apologies for the delayed reply. Thanks for the info.
$ cat /etc/rpi-issue
Raspberry Pi reference 2022-09-06
[...]
$ hostnamectl
[...]
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 6.1.19-v8+
Architecture: arm64
$ sudo aa-enabled
No - disabled at boot.
$ sudo aa-status
apparmor module is loaded.
apparmor filesystem is not mounted.
Am I correct to say that if I run the apparmor_parser command mentioned on the Unbound guide and get this error (because it is disabled as here), I can simply ignore that step and move on? Or is some alternative command needed (this all relates to the logging info at the end of the guide).
Mine appears to be working without having created an AppArmor exception, presumably because it's not controlling anything as it's not enabled.