You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have both music-assistant-server and a python-matter-server running on the same physical host via docker-compose. Both are heavily reliant on mdns, and therefore each needs network_mode: host . Each container is somehow listening on port 5353 on every interface of the host machine, which I think may be causing spurious behavior in each container, but I cannot be sure of that. In the case of music-assistant, this manifests as players very randomly appearing and disappearing, especially while not actively playing anything.
I have tried searching for the better part of a day now and am not finding any good answers to the following question: How do I disable music-assistant starting up its own avahi listeners, in favor of using mdns services from either a systemd controlled avahi-daemon, or second choice an avahi-daemon container instead?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have both music-assistant-server and a python-matter-server running on the same physical host via docker-compose. Both are heavily reliant on mdns, and therefore each needs network_mode: host . Each container is somehow listening on port 5353 on every interface of the host machine, which I think may be causing spurious behavior in each container, but I cannot be sure of that. In the case of music-assistant, this manifests as players very randomly appearing and disappearing, especially while not actively playing anything.
I have tried searching for the better part of a day now and am not finding any good answers to the following question: How do I disable music-assistant starting up its own avahi listeners, in favor of using mdns services from either a systemd controlled avahi-daemon, or second choice an avahi-daemon container instead?
Beta Was this translation helpful? Give feedback.
All reactions