Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
User defined networks like overlays support DNS resolution through Docker Embedded DNS which needs the container name (–name parameter value in docker run) to be a FQDN for container names to be resolved - Please refer documentation https://docs.docker.com/v17.09/engine/userguide/networking/configure-dns/
However Yarn sets the container name to the container's id which is not DNS friendly(eg: container_e26_1519402686002_0035_01_000003) and is not a FQDN.
The proposal is to set a FQDN(eg: ctr-e26-1519402686002-0035-01-000003.domain-name) as the docker container's name for containers to be able to communicate to each other via hostnames in user defined networks like overlays, bridges etc. The domain name will be picked up from the YARN DNS registry configuration (hadoop.registry.dns.domain-name)
Attachments
Issue Links
- relates to
-
YARN-7994 Add support for network-alias in docker run for user defined networks
- Resolved