[
https://issues.apache.org/jira/browse/YARN-8776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667749#comment-16667749
]
Hadoop QA commented on YARN-8776:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} YARN-8776 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | YARN-8776 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12946094/YARN-8776.004.patch |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/22372/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Container Executor change to create stdin/stdout pipeline
> ---------------------------------------------------------
>
> Key: YARN-8776
> URL: https://issues.apache.org/jira/browse/YARN-8776
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zian Chen
> Assignee: Zian Chen
> Priority: Major
> Labels: Docker
> Attachments: YARN-8776.001.patch, YARN-8776.002.patch,
> YARN-8776.003.patch, YARN-8776.004.patch
>
>
> The pipeline is built to connect the stdin/stdout channel from WebSocket
> servlet through container-executor to docker executor. So when the WebSocket
> servlet is started, we need to invoke container-executor “dockerExec” method
> (which will be implemented) to create a new docker executor and use “docker
> exec -it $ContainerId” command which executes an interactive bash shell on
> the container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
