Jim Brennan commented on YARN-8027:

{quote}We should look into whether it is a bug in that version of Docker. I see 
a couple of tickets regarding adding support for setting hostname when 
net=host, which would indicate that is a valid setting. I have not dug far 
enough to determine which versions are supposed to support it.
[~billie.rinaldi], I think it is actually the opposite. Specifying --hostname 
with --net=host was broken before docker 1.13.1, which is why it didn't cause 
us a problem. In 1.13.1 though, it works, which breaks our ability to resolve 
the hostname, since we are not using Registry DNS.

I agree with [~jlowe] and [~shaneku...@gmail.com], we should only set the 
hostname when Registry DNS is enabled, as long as this is indeed always the 
case. We haven't experimented with user-defined networks here - is it the case 
that Registry DNS must always be used for user-defined networks?

> 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