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
The current solution does not support resolving the .local domain name resolution that is generally supported by balenaOS devices.
The issue here is, that for this feature the avahi/mdns publisher running inside the balenaOS is used. This service is listening on a fixed / reserved IP (224.0. 0.251 ) and needs to bind / listen on port 5353. This port is already in use on macOS for bonjour service (macOS mDNS publisher service).
Hence, mapping the container to 5353 on the host doesn't work.
I've no idea on how to solve this, maybe in the future the .local resolution needs to be address in some central / cloud managed service.
The text was updated successfully, but these errors were encountered:
fisehara
changed the title
mDNS support / avahi inside balenaOS container
mDNS publisher inside balenaOS container not working - failing port mapping
Dec 13, 2021
The current solution does not support resolving the .local domain name resolution that is generally supported by balenaOS devices.
The issue here is, that for this feature the avahi/mdns publisher running inside the balenaOS is used. This service is listening on a fixed / reserved IP (224.0. 0.251 ) and needs to bind / listen on port 5353. This port is already in use on macOS for bonjour service (macOS mDNS publisher service).
Hence, mapping the container to 5353 on the host doesn't work.
I've no idea on how to solve this, maybe in the future the .local resolution needs to be address in some central / cloud managed service.
The text was updated successfully, but these errors were encountered: