[
https://issues.apache.org/jira/browse/YARN-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306211#comment-15306211
]
tangzhankun commented on YARN-5168:
-----------------------------------
[~hex108],
Yes. Maybe I'm not clear enough. The port conflicts happens when container
network uses host mode or bridge mode with port mapping. I got your points now
and agree with it. So if we want to push this further, we should split it into
several sub-tasks:
1. Add "-p" and "-P" for docker run time with consideration of host port
conflicts
2. Utilize YARN registry to register the container port for query
3. A native way for service discovery between containers. Maybe DNS similar
mechanism.
And do you have any plan for a proposal? If no, we are glad to help and you can
also assign this to me or [~zyluo].
> 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
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
