[
https://issues.apache.org/jira/browse/YARN-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688861#comment-16688861
]
Eric Yang commented on YARN-5168:
---------------------------------
[~liuxun323] patch 001 is a draft patch to aggregate exposed port information
to YARN service that I worked on the last 2 days. Maybe you can make use of
this? What's remaining:
# add the new bits of json output to YARN UI 2
# make sure unit test and check style can pass.
# Remove the container-executor.c hack of hard coding -P
> 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-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: [email protected]
For additional commands, e-mail: [email protected]
