You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by gi...@git.apache.org on 2017/08/17 19:18:27 UTC
[GitHub] csantanapr commented on issue #2641: Install composer in its own layer
csantanapr commented on issue #2641: Install composer in its own layer
URL: https://github.com/apache/incubator-openwhisk/pull/2641#issuecomment-323168449
The issue is hard to explain when docker tries to use a cache layer, for some reason is not finding composer.
The only think I can think is that that there was a previous run that it didn't exit with error for the `| php ...`
The error looks like this:
```
Step 2/9 : RUN apk update && apk upgrade && apk add postgresql-dev icu icu-libs icu-dev freetype-dev libjpeg-turbo-dev libpng-dev libxml2-dev && docker-php-ext-install opcache mysqli pdo_mysql pdo_pgsql intl bcmath zip gd soap && cd /tmp && curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/bin --filename=composer
---> Using cache
---> 1612c7c99f05
Step 3/9 : RUN mkdir -p /action/src
---> Using cache
---> 2a8b4bd4b6c8
Step 4/9 : COPY composer.json /action
---> Using cache
---> d4459dc8fd95
Step 5/9 : RUN cd /action && /usr/bin/composer install --no-plugins --no-scripts --prefer-dist --no-dev -o && rm composer.lock
---> Running in 856b4de3df61
[91m/bin/sh: /usr/bin/composer: not found
The command '/bin/sh -c cd /action && /usr/bin/composer install --no-plugins --no-scripts --prefer-dist --no-dev -o && rm composer.lock' returned a non-zero code: 127
[0m
...
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services