-
Notifications
You must be signed in to change notification settings - Fork 4
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
avahi2dns timeout #8
Comments
Continuing the discussion from #7. It seems like Or is |
I can disable avahi to show the difference
same container, just with an |
OK, so A few DNS queries failing when Avahi isn't running doesn't seem like a huge deal and fairly tolerant? I guess we could a retry or two, but it's unclear if that might help your case? Both this project and the one which connects to Avahi (https://github.com/holoplot/go-avahi) use https://github.com/godbus/dbus and I haven't found any way to configure a timeout or retry. |
But I haven't found a single query to go through yet; it always times out :( The timeouts feel quite long too, like a few seconds? Since this is running on a fast server (not a raspberry pi) and this is within its own docker container, there shouldn't be any performance issue? And looking at the code, it does look like all error handling is in place; however actually getting 'something' from avahi is failing it seems. here's my compose file
|
@LouisBrunner any thoughts or insights how I could start resolving local domains? With zero successful resolvings I wonder what could possibly be going on; seems more like a bug/misconfiguration then a timeout issue ... |
It looks like it could be a configuration issue, yeah. Could you try using something like |
I have a docker container, where I install only avahi2dns and avahi itself.
While there's a sleep during startup needed due to #7 both services start up.
However avahi2dns complains about timeout, which makes me think it failed to connect to the dbus service.
I wonder if the connection to the system bus is properly error handled. In my container, the socket is mounted and available under
/run/dbus/system_bus_socket
and avahi is happily using it (this is actually a volume mount so that multiple containers can make use of the same socket, including the host itself. For all other services, this is working fine.The text was updated successfully, but these errors were encountered: