You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Suma Shivaprasad (JIRA)" <ji...@apache.org> on 2018/03/01 02:31:00 UTC
[jira] [Created] (YARN-7987) Docker container name(--name) needs to
be DNS friendly for DNS resolution to work in user defined networks.
Suma Shivaprasad created YARN-7987:
--------------------------------------
Summary: Docker container name(--name) needs to be DNS friendly for DNS resolution to work in user defined networks.
Key: YARN-7987
URL: https://issues.apache.org/jira/browse/YARN-7987
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Suma Shivaprasad
Assignee: Suma Shivaprasad
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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org