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 "Jim Brennan (JIRA)" <ji...@apache.org> on 2018/03/13 22:21:00 UTC

[jira] [Updated] (YARN-8027) Setting hostname of docker container breaks for --net=host in docker 1.13

     [ https://issues.apache.org/jira/browse/YARN-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Brennan updated YARN-8027:
------------------------------
    Attachment: YARN-8027.001.patch

> 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
>         Attachments: YARN-8027.001.patch
>
>
> 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
(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