Hi, first post here!
I have the wireguard container running in a Debian 6.1.55 x64 system. It works fine, or at least it seems fine, until I check the system logs and I find an endless stream of log entries like this:
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2067._ssh._tcp.local. for type 33, reloading config …
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2067.local. for type 28, reloading config …
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2067._ssh._tcp.local. for type 16, reloading config …
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2068._ssh._tcp.local. for type 33, reloading config …
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2068.local. for type 28, reloading config …
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2068._ssh._tcp.local. for type 16, reloading config …
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2069._ssh._tcp.local. for type 33, reloading config …
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2069.local. for type 28, reloading config …
3/31/24 2:33 AM mdnsd veth8402cdc: conflicting name detected mcserver-2069._ssh._tcp.local. for type 16, reloading config …
with each iteration the name (mcserver) gets a higher number and it never stops. After many days of working fine, I recently found out my system stuck at 100% cpu usage. I checked the logs and this was the only unusual thing going on. As soon as I stop the container, the log entries stop as well.
veth8402cdc seems to be the name of the virtual network interface that belongs to the wireguard container
Thanks in advance for any tips you may provide!