Yes, I sent a pull request to fix an issue there:
1 Like
One thing that could explain this if ProtectHostname=true was set in the container but not for the host synapse.service But if both override-hardened.conf are identical than that seems unlikely and afaict, the zz-lxc-service.conf thing doesn’t bring in ProtectHostname=true. Rather it’s set in override-hardened.conf. Can you double-check that ProtectHostname=true is present both on the host and in the container?
What’s your systemd version on the host and systemd version in the container?
I can confirm that ProtectHostname=true both in the container and on the host.
systemd host: 250.2-2
systemd container: 250-4
1 Like
image-archlinux [Jenkins] is rebuilding now, the updated images will likely be live in a couple of hours.
2 Likes