Control: tags -1 + confirmed Control: forwarded https://discuss.linuxcontainers.org/t/systemd-hostnamed-unable-to-start-on-lxd-5-0-containers/17454
Hi Bagas, Michael, At first glance, this looks like an apparmor problem. Unfortunately all the issues that have been mentioned previously are about five years old. Ubuntu has carried custom patches for the kernel and apparmor in the past, but at least the relevant kernel changes seem to have been merged quite a while back[1]. I will see what I can figure out on my end and update this when I know more. > 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. Mathias [1] -- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4
signature.asc
Description: This is a digitally signed message part
