Jason Lowe commented on YARN-8027:

Overriding the hostname only makes sense if the new name is resolvable.  
Otherwise we're going to break any application that assumes they can lookup the 
hostname, which seems like a reasonable assumption to me.  The names we want to 
use for the hostname are only going to be resolvable when Registry DNS is 
enabled, so the hostname override behavior should be tied to that.

> Setting hostname of docker container breaks for --net=host in docker 1.13
> -------------------------------------------------------------------------
>                 Key: YARN-8027
>                 URL: https://issues.apache.org/jira/browse/YARN-8027
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 3.0.0
>            Reporter: Jim Brennan
>            Assignee: Jim Brennan
>            Priority: Major
> In DockerLinuxContainerRuntime:launchContainer, we are adding the --hostname 
> argument to the docker run command to set the hostname in the container to 
> something like:  ctr-e84-1520889172376-0001-01-000001.
> This does not work when combined with the --net=host command line option in 
> Docker 1.13.1.  It causes multiple failures when the client tries to resolve 
> the hostname and it fails.
> We haven't seen this before because we were using docker 1.12.6 which seems 
> to ignore --hostname when you are using --net=host.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to