You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2019/04/05 23:55:00 UTC

[jira] [Commented] (YETUS-833) start-build-env is failing

    [ https://issues.apache.org/jira/browse/YETUS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811359#comment-16811359 ] 

Allen Wittenauer commented on YETUS-833:
----------------------------------------

-00:
* I give up.

> start-build-env is failing
> --------------------------
>
>                 Key: YETUS-833
>                 URL: https://issues.apache.org/jira/browse/YETUS-833
>             Project: Yetus
>          Issue Type: Bug
>          Components: build
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>            Priority: Major
>         Attachments: YETUS-833.00.patch
>
>
> From the way it appears, the apache/yetus-base image is getting the last RUN statement treated as a CMD statement:
> {code}
> $ docker inspect  apache/yetus-build-501:master
> ...
>             "Cmd": [
>                 "/bin/bash",
>                 "-o",
>                 "pipefail",
>                 "-c",
>                 "apt-get -q update     && apt-get -q install --no-install-recommends -y nodejs npm     && apt-get clean     && rm -rf /var/lib/apt/lists/* &&     ln -s /usr/bin/nodejs /usr/bin/node &&     npm install -g npm@latest &&     npm install -g jshint"
>             ],
> ...
> {code}
> This might be a bug with hub.docker.com. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)