-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker0
bind error spam
#1192
Comments
If your Docker installation doesn't have IPv6 enabled then you can just disable multicasting by setting |
It actually does:
{
"ipv6": true,
"fixed-cidr-v6": "fd12:3452:789a:1::/64",
"experimental": true,
"ip6tables": true,
"dns": ["192.168.4.100"],
"log-opts": {
"max-size": "10m",
"max-file": "1"
},
"storage-driver": "overlay2",
"builder": {
"Entitlements": {
"security-insecure": true
}
}
} will disable the listening in the Yggdrasil config |
I don't really know Docker's bridge networking well enough to understand why it would be trying to assign Yggdrasil just tries to select a link-local address to use from interfaces that are up and connected, and it does so continuously to respond to changes in network links, i.e. a network cable or Wi-Fi network connects/disconnects. That said there's every possibility that multicast discovery won't really work properly under Docker anyway, in which case you may just want to disable it anyway. |
Any way to add an exception / timed out on retries function on ports/interfaces which are misbehaving towards adding the multicast listener? |
Solution is to use RegEx: When using panic: regexp: Compile(`^(?!docker).*`): error parsing regexp: invalid or unsupported Perl syntax: `(?!`
goroutine 1 [running]:
/opt/hostedtoolcache/go/1.20.13/x64/src/regexp/regexp.go:319 +0xbb
main.main()
/home/runner/work/yggdrasil-go/yggdrasil-go/cmd/yggdrasil/main.go:245 +0x1fc9 |
Yggdrasil node is spamming
yggdrasil[5177]: 2024/10/20 10:19:16 Not multicasting on docker0 due to error: listen tcp [fe80::1%docker0]:0: bind: cannot assign requested address
in the/var/log/messages
every second.The text was updated successfully, but these errors were encountered: