[
https://issues.apache.org/jira/browse/YARN-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726565#comment-16726565
]
Xun Liu commented on YARN-5168:
-------------------------------
[~eyang], Please help me review the code, thank you! :)
> Add port mapping handling when docker container use bridge network
> ------------------------------------------------------------------
>
> Key: YARN-5168
> URL: https://issues.apache.org/jira/browse/YARN-5168
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jun Gong
> Assignee: Xun Liu
> Priority: Major
> Labels: Docker
> Attachments: YARN-5168.001.patch, YARN-5168.002.patch,
> YARN-5168.003.patch, YARN-5168.004.patch, YARN-5168.005.patch,
> YARN-5168.006.patch, YARN-5168.007.patch, YARN-5168.008.patch,
> YARN-5168.009.patch, YARN-5168.010.patch, YARN-5168.011.patch,
> YARN-5168.012.patch, YARN-5168.013.patch, YARN-5168.014.patch,
> YARN-5168.015.patch, YARN-5168.016.patch, YARN-5168.017.patch,
> YARN-5168.018.patch, YARN-5168.019.patch, YARN-5168.020.patch,
> exposedPorts1.png, exposedPorts2.png
>
>
> YARN-4007 addresses different network setups when launching the docker
> container. We need support port mapping when docker container uses bridge
> network.
> The following problems are what we faced:
> 1. Add "-P" to map docker container's exposed ports to automatically.
> 2. Add "-p" to let user specify specific ports to map.
> 3. Add service registry support for bridge network case, then app could find
> each other. It could be done out of YARN, however it might be more convenient
> to support it natively in YARN.
--
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
