[ 
https://issues.apache.org/jira/browse/YARN-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724279#comment-16724279
 ] 

Eric Yang commented on YARN-5168:
---------------------------------

[~liuxun323] Thank you for the patch.  Container newInstance is probably better 
to stay as 7 parameters to prevent API breakage in Hadoop 3.3.0.  Like 
setResource, setExposedPort is optional and not used in most of the places.  It 
would be better to call setExposedPort explicitly method when ports are 
required.  This will reduce the size of the patch significantly. 

> 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, 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

Reply via email to