Laurent Bigonville

minissdpd shows: ``` avr 18 19:38:00 fornost minissdpd[1226]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, enp5s0): Address already in use avr 18 19:38:00 fornost minissdpd[1226]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, enp5s0): Address already in use avr 18 19:38:00...

I'm getting this every 2 or 3 minutes on my machine here The IPv6 router is refreshing the dynamically assigned address, I guess?

Like I said in my initial report, the multicast membership with IPv6 is made using the interface, not the local address. So even if the IPv6 address on an interface...

Any idea? I'm still seeing that when deploying on EKS

I can confirm that adding a `securityContext` to the container fixed the problem for me here, even with `runAsNonRoot` set as true ```yaml securityContext: fsGroup: 2000 runAsNonRoot: true runAsUser: 1000...

Well there is some difference between kind and EKS then But note that all the other deployments have an explicit `securityContext` defined

Thanks for your reply systemd generator are described [here]( https://www.freedesktop.org/wiki/Software/systemd/Generators) ([full doc](https://www.freedesktop.org/software/systemd/man/systemd.generator.html)) Generator are running really early during the boot, earlier than .services started by the multi-user target Creating the...

I'm not sure there is an override. Is it really a problem to store the pid of the process running as root instead of the unprivileged one?

Apparently the unpriv process complains and continues to run if the privileged process is killed ``` avr 23 20:31:05 fornost upsmon[9846]: upsmon parent process died - shutdown impossible avr 23...

Oh indeed we could prevent it to go into the background, this is even advised by systemd developers. About reloading, we probably need to add the ExecReload= in the systemd...