[
https://issues.apache.org/jira/browse/YARN-9003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746448#comment-16746448
]
Jim Brennan commented on YARN-9003:
-----------------------------------
[~eyang],
{quote}
Docker does not support multiple network interface using docker CLI. What I
observed via docker run --net=bridge --net=overlay was wrong. When overlay
network is specified, docker will automatically add bridge network interface in
addition to overlay network interface.
Docker run with multiple --net parameter is still a problem in Docker 35543. We
may revisit this when Docker add support for multiple --net parameter.
{quote}
So should this Jira be closed as invalid?
> Support multi-homed network for docker container
> ------------------------------------------------
>
> Key: YARN-9003
> URL: https://issues.apache.org/jira/browse/YARN-9003
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Yang
> Priority: Major
> Labels: docker
> Attachments: YARN-9003.001.patch, YARN-9003.002.patch,
> YARN-9003.003.patch, YARN-9003.004.patch, YARN-9003.005.patch,
> YARN-9003.006.patch, YARN-9003.007.patch, YARN-9003.008.patch,
> YARN-9003.009.patch
>
>
> Docker network can be defined as configuration properties - docker.network to
> setup docker container to connect to a specific network in YARN service.
> Docker can run multi-homed network by specifying --net=bridge
> --net=private-net. This is useful to expose small number of front end
> container and ports, while the rest of the infrastructure runs in private
> network. This task is to add support for specifying multiple docker networks
> to YARN service and docker support.
--
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
