On 6/24/23 22:19, Mathias Gibbens wrote: >> systemd-hostnamed.service is probably also affected, but in my case I >> paved over the issue by setting PrivateNetwork=no in an override. > > For the moment setting PrivateNetwork=no for affected services is > probably a better approach than totally removing the container's > apparmor profile. >
Hi Mathias, sorry for late reply. Indeed, overriding affected services with PrivateNetwork=no works. Thanks for the better workaround! -- An old man doll... just what I always wanted! - Clara
