Repository navigation
Conversation
…works A container's mDNS announcements reach the host on the interface of the container's network and go no further, and they name an address that only the host can reach. Applications that rely on being discovered, such as a HomeKit bridge, are therefore invisible to the rest of the network even when their port is published. With --mdns, the runtime helper finds the services that the container announces and registers each one with the host's mDNS responder on the host's other interfaces, as a service of the host on the published host port. The registrations follow the container: TXT record and port changes are carried over, and a service is withdrawn when the container stops announcing it or stops. - Only services on published ports are advertised, and --mdns without --publish is rejected. - Only services whose host resolves to the container's address are advertised, because the host's own services and other containers are visible on the same interface. - A service is never registered on the container's network, where the container owns the name, and at most once per IP network, because two registrations on one link can conflict with each other when the TXT record is updated. The option is off by default and stored in the container configuration. See docs/architecture/mdns.md.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A container's mDNS announcements reach the host on the interface of the container's network and go no further, and they name an address that only the host can reach. Applications that rely on being discovered, such as a HomeKit bridge, are therefore invisible to the rest of the network even when their port is published.
With
--mdns, the runtime helper finds the services that the container announces and registers each one with the host's mDNS responder on the host's other interfaces, as a service of the host on the published host port. The registrations follow the container: TXT record and port changes are carried over, and a service is withdrawn when the container stops announcing it or stops.--mdnswithout--publishis rejected.The option is off by default and stored in the container configuration. See
docs/architecture/mdns.md.Type of Change
Testing