-
Notifications
You must be signed in to change notification settings - Fork 217
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
OpenThread Border Router - Container runs multiple mDNS stacks #2280
Comments
Sounds good to disable avahi in docker. Contributions are welcome! |
kevinanderson1
added a commit
to kevinanderson1/ot-br-posix
that referenced
this issue
May 10, 2024
Ensure the Avahi daemon is installed and started only when OTBR_MDNS == "avahi". This prevents multiple mDNS stacks from running especially in container environments.
kevinanderson1
added a commit
to kevinanderson1/ot-br-posix
that referenced
this issue
May 10, 2024
Ensure the Avahi daemon is installed and started only when OTBR_MDNS == "avahi". This prevents multiple mDNS stacks from running especially in container environments.
kevinanderson1
added a commit
to kevinanderson1/ot-br-posix
that referenced
this issue
May 10, 2024
Ensure the Avahi daemon is installed and started only when OTBR_MDNS == "avahi". This prevents multiple mDNS stacks from running especially in container environments.
kevinanderson1
added a commit
to kevinanderson1/ot-br-posix
that referenced
this issue
May 11, 2024
Ensure the Avahi daemon is installed and started only when OTBR_MDNS == "avahi". This prevents multiple mDNS stacks from running especially in container environments.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The container at docker.io/openthread/otbr:latest runs
avahi-daemon
andmdns
resulting in mdns name conflicts.To Reproduce
docker.io/openthread/otbr@sha256:3e46f5096405149aa13da8485f8a9dabb9a3cdaaf3e85f2a89217c116cc0bca2
ss -lpntu | grep 5353
I'm using the following systemd quadlet to run the container.
Expected behavior
The container to run and not experience host name conflicts resulting in mDNS withdraws and publishing under new host names.
Console/log output
Additional context Add any other context about the problem here.
None
** Additional Comments**
It appears
mdnsd
is the defaultmdns
stack based on the contents of the Dockerfile. Would it be safe to just disable the avahi-daemon from starting by default? I'd be willing to take an attempt at a PR to resolve the issue if this is confirmed as a valid bug.The text was updated successfully, but these errors were encountered: