This was fixed in ubuntu maintic, but not yet SRU'd to focal, jammy, or lunar since this "fix" just eliminates harmless warnings, which is not worth backporting to old releases.
Cloud-init users that see warnings due to apparmor such as
execve (/bin/true, ...): Permission denied
due to apparmor blocking execution of /bin/true may be concerned about problems associated with this error, but rest assured that apparmor blocking /bin/true accomplishes the same thing as apparmor allowing /bin/true (no side-effects are allowed by hook scripts), so this warning is just noise and can be safely ignored.
Cloud-init users on these releases that wish to see no apparmour warnings might locally include this rule themselves via:
This was fixed in ubuntu maintic, but not yet SRU'd to focal, jammy, or lunar since this "fix" just eliminates harmless warnings, which is not worth backporting to old releases.
Cloud-init users that see warnings due to apparmor such as
execve (/bin/true, ...): Permission denied
due to apparmor blocking execution of /bin/true may be concerned about problems associated with this error, but rest assured that apparmor blocking /bin/true accomplishes the same thing as apparmor allowing /bin/true (no side-effects are allowed by hook scripts), so this warning is just noise and can be safely ignored.
Cloud-init users on these releases that wish to see no apparmour warnings might locally include this rule themselves via:
echo " /bin/true Uxr," > /etc/apparmor. d/local/ sbin.dhclient