[ https://issues.apache.org/jira/browse/YARN-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689356#comment-16689356 ]
Charo Zhang edited comment on YARN-8986 at 11/16/18 3:41 PM: ------------------------------------------------------------- [~eyang] Thanks for you suggestions. About 2/3/4 point, i have Modified according to you opinion. but about the first suggestion: 1, network name is only allowed by yarn.nodemanager.runtime.linux.docker.allowed-container-networks configuration, so i think "null >/dev/null && rm -rf *" can not pass to the commmand. 2, Another reason, i didn't find a better way to get network type except command with pipe.:( was (Author: charo zhang): [~eyang] Thanks for you suggestions. About 2/3/4 point, i will change and test later. but about the first suggestion: 1, network name is only allowed by yarn.nodemanager.runtime.linux.docker.allowed-container-networks configuration, so i think "null >/dev/null && rm -rf *" can not pass to the commmand. 2, Another reason, i didn't find a better way to get network type except command with pipe.:( > publish all exposed ports to random ports when using bridge network > ------------------------------------------------------------------- > > Key: YARN-8986 > URL: https://issues.apache.org/jira/browse/YARN-8986 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn > Affects Versions: 3.1.1 > Reporter: Charo Zhang > Assignee: Charo Zhang > Priority: Minor > Labels: Docker > Fix For: 3.1.2 > > Attachments: YARN-8986.patch > > > it's better to publish all exposed ports to random ports(-P) or support port > mapping(-p) for bridge network when using bridge network for docker container. > -- 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