[
https://issues.apache.org/jira/browse/HDDS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693471#comment-16693471
]
Hadoop QA commented on HDDS-852:
--------------------------------
| (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:blue}0{color} | {color:blue} docker {color} | {color:blue} 0m
7s{color} | {color:blue} Dockerfile
'/home/jenkins/jenkins-slave/workspace/PreCommit-HDDS-Build/sourcedir/dev-support/docker/Dockerfile'
not found, falling back to built-in. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 3m
14s{color} | {color:red} Docker failed to build yetus/hadoop:date2018-11-20.
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDDS-852 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12948885/HDDS-852-docker-hadoop-runner.002.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HDDS-Build/1767/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Remove unnecessary stdout printing from apache/hadoop-runner
> ------------------------------------------------------------
>
> Key: HDDS-852
> URL: https://issues.apache.org/jira/browse/HDDS-852
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Attachments: HDDS-852-docker-hadoop-runner.001.patch,
> HDDS-852-docker-hadoop-runner.002.patch
>
>
> Latest apache/hadoop-runner always prints out an informal line before
> executing anything:
> {code}
> docker run apache/hadoop-runner ls
> Setting up environment!
> ...
> {code}
> This "Setting up environment!" line is always there.
> Here I propose to delete this one line from the starter script.
> REASONING:
> As I proposed in HDDS-851 we can provide very easy way to getting started
> with ozone with executing commands inside the official apache/ozone docker
> image:
> For example:
> {code}
> docker run apache/ozone cat docker-compose.yaml > docker-compose.yaml
> {code}
> This pattern (executing command inside + redirecting the output) can't be
> done with this generic "Setting up environment!" line.
> I think it's safe to delete as all the optional steps (kerberos init, wait
> for additional services, generate configs, etc) could have separated
> (non-default) logging lines.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
