I don’t have any more ideas since I haven’t played with containers much :(
Feels like the NPM command is not being ran on the container. Does it work
if you remove the NPM stuff?
On Mon, Sep 17, 2018 at 03:57 Blau Gil wrote:
> Hi Jan,
>
> Thank you for assisting.
> Yes the container runs on
Hi Jan,
Thank you for assisting.
Yes the container runs on its own, only when I try to run the container
image with Jenkins it fails.
Any idea what I can do to resolve this?
Thanks,
--Gil.
On Thu, 23 Aug 2018 at 04:04, Jan Monterrubio
wrote:
> Does the container work on its own?
>
> Looks
Hi Jan,
Thank you for assisting.
Yes the container runs on its own, only when I try to run the container
image with Jenkins it fails.
Any idea what I can do to resolve this?
Thanks,
--Gil.
On 23 August 2018 at 04:03, Jan Monterrubio
wrote:
> Does the container work on its own?
>
> Looks like
Does the container work on its own?
Looks like you have this part in the container:
"RUN apk add --no-cache --virtual .gyp \
python \
make \
g++ \
git \
&& npm install --quit && npm cache clean --force \
&& apk del .gyp"
Which runs npm install
On Wed, Aug 22, 2018 at 6:08 AM gil wrote:
>
Anyone?
On Sunday, 12 August 2018 11:28:54 UTC+3, gil wrote:
>
> Trying to tun a podTemaplate with the following containerTemplate, we get
> the following error:
>
> npm ERR! path /home/jenkins/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent
Trying to tun a podTemaplate with the following containerTemplate, we get
the following error:
npm ERR! path /home/jenkins/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open
'/home/jenkins/package.json'
npm ERR! enoent