Hello,
I’ve run into similar issues after updating to the 2022.11 release. My HA instance is a supervised version on a Raspbian Bullseye installation. Some of the issues were easy to resolve, here’s what I did:
- AppArmor
Make sure apparmor is installed (it was already for me) and enable it with a kernel boot parameter. E.g. if you are running HA on a Raspberry Pi add “apparmor=1 security=apparmor” to /boot/cmdline.txt - Systemd-Resolved
Enable the systemd-resolved service “systemctl enable systemd-resolved.service && systemctl start systemd-resolved”.
You can check if it’s working with e.g. “systemd-resolve home-assistant.io”. - CGroup version
I was using docker (unknowningly) with CGroup version 2, which is still not fully supported. Seemed to work fine, though. Nevertheless, you can force version 1 with a kernel parameter in /boot/cmdline.txt, add “systemd.unified_cgroup_hierarchy=0”.
You can also check your version with “grep cgroup /proc/mounts”, it will print “cgroup” for version 1 and “cgroup2” for version 2 in the first column.
After a reboot the corresponding warnings were gone. Still working on the Sytemd Journal issue…
Thomas