[
https://issues.apache.org/jira/browse/YARN-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386113#comment-16386113
]
Shane Kumpf commented on YARN-7987:
-----------------------------------
{quote}Created YARN-7994 to track adding support for network-alias
{quote}
Thanks, [~suma.shivaprasad]! Do you think we can close this issue or do we
still need to explore this after YARN-7994?
> 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
> Priority: Major
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
