Bug#1110985: unbound: will not start with AppArmor in enforcing mode

[Michael Tokarev]

On 13.08.2025 12:00, Brian Turek wrote:

Package: unbound
Version: 1.22.0-2
Severity: important

Dear Maintainer,

    * What led up to the situation?
      I recently just upgraded my Proxmox host from Debian 12 to 13 as well as 
Proxmox 8 to 9. Upon reboot, my existing/working installation of unbound did 
not start
    * What exactly did you do (or not do) that was effective (or
      ineffective)?
      After troubleshooting, I determined something in the stock AppArmor 
profile was blocking unbound from starting. Putting the unbound AppArmor 
profile into complain mode yielded ambiguous socket denial errors. Disabling 
the AppArmor profile allowed unbound to start correctly. I also purged my 
existing unbound install (reverting to stock configs) and it too would not start

What does it deny, exactly?

Thanks,

/mjt