[ https://issues.apache.org/jira/browse/YARN-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685611#comment-16685611 ]
Eric Yang edited comment on YARN-5168 at 11/13/18 8:33 PM: ----------------------------------------------------------- The current plan is to expose this information through YARN service because YARN service AM can aggregate container information. {code} { "components": [ { "artifact": { "id": "hadoop/centos:latest", "type": "DOCKER" }, "configuration": { "env": { }, "files": [ ], "properties": { "docker.network": "bridge,hadoop" } }, "containers": [ { "bare_host": "eyang-5.example.com", "component_instance_name": "ping-2", "hostname": "ping-2.abc.hbase.ycluster", "id": "container_1542058458438_0002_01_000023", "ip": "172.17.0.20", "launch_time": 1542133678396, "state": "READY", "exposed_ports": { "8080/tcp": "0.0.0.0:32769", "8443/tcp": "0.0.0.0:32768" }, }, { "bare_host": "eyang-5.example.com", "component_instance_name": "ping-0", "hostname": "ping-0.abc.hbase.ycluster", "id": "container_1542058458438_0002_01_000024", "ip": "172.17.0.20", "launch_time": 1542133737566, "state": "READY" } ], "decommissioned_instances": [ "ping-1" ], "dependencies": [], "launch_command": "sleep,10000", "name": "ping", "number_of_containers": 2, "quicklinks": [], "resource": { "additional": {}, "cpus": 1, "memory": "256" }, "restart_policy": "ALWAYS", "run_privileged_container": true, "state": "STABLE" } ], "configuration": { "env": {}, "files": [], "properties": {} }, "dependencies": [], "id": "application_1542058458438_0002", "kerberos_principal": { "keytab": "file:///etc/security/keytabs/hbase.service.keytab", "principal_name": "hbase/_h...@example.com" }, "lifetime": -1, "name": "abc", "quicklinks": {}, "state": "STABLE", "version": "5" } {code} was (Author: eyang): The current plan is to expose this information through YARN service because YARN service AM can aggregate container information. {code} { "components": [ { "artifact": { "id": "hadoop/centos:latest", "type": "DOCKER" }, "configuration": { "env": { }, "files": [ ], "properties": { "docker.network": "bridge,hadoop" } }, "containers": [ { "bare_host": "eyang-5.example.com", "component_instance_name": "ping-2", "hostname": "ping-2.abc.hbase.ycluster", "id": "container_1542058458438_0002_01_000023", "ip": "172.17.0.20", "launch_time": 1542133678396, "state": "READY", "exposed_ports": [ "8080/tcp", "8443/tcp" ], }, { "bare_host": "eyang-5.example.com", "component_instance_name": "ping-0", "hostname": "ping-0.abc.hbase.ycluster", "id": "container_1542058458438_0002_01_000024", "ip": "172.17.0.20", "launch_time": 1542133737566, "state": "READY" } ], "decommissioned_instances": [ "ping-1" ], "dependencies": [], "launch_command": "sleep,10000", "name": "ping", "number_of_containers": 2, "quicklinks": [], "resource": { "additional": {}, "cpus": 1, "memory": "256" }, "restart_policy": "ALWAYS", "run_privileged_container": true, "state": "STABLE" } ], "configuration": { "env": {}, "files": [], "properties": {} }, "dependencies": [], "id": "application_1542058458438_0002", "kerberos_principal": { "keytab": "file:///etc/security/keytabs/hbase.service.keytab", "principal_name": "hbase/_h...@example.com" }, "lifetime": -1, "name": "abc", "quicklinks": {}, "state": "STABLE", "version": "5" } {code} > 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: Eric Yang > Priority: Major > Labels: Docker > > 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