appserver-images icon indicating copy to clipboard operation
appserver-images copied to clipboard

Error building images - HTTP error 404

Open davsclaus opened this issue 10 years ago • 2 comments

Hi

At our fabric8 fork we have slightly changed the images to be from a fabric8 base image which we need for kubernetes/os environments.

Though when we build the images using

 node docker-appserver.js --build --server=jetty

We often get errors about not found

++++++++ ERROR +++++++++++
The command [/bin/sh -c cd /opt && jar xf /tmp/jetty.zip] returned a non-zero code: 1    8
fabric8/jetty-8:8.1.16.v20140903
/Users/davsclaus/workspace/docker-appserver/docker-appserver.js:242
                        if (error) { throw error; }
                                           ^
Error: HTTP code is 404 which indicates error: no such image - no such id: fabric8/jetty-7:7.6.16.v20140903

    at /Users/davsclaus/workspace/docker-appserver/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:207:17

I just wonder if you have error seen such kind of error from the original code base?

Besides me, then @iocanel also has these errors.

davsclaus avatar Apr 02 '15 07:04 davsclaus

btw the fork is here https://github.com/fabric8io/docker-appserver

davsclaus avatar Apr 02 '15 07:04 davsclaus

The error is a bit misleading: The 404 happens when trying to tag the image, but the image couldn't be created because of the error before:

The command [/bin/sh -c cd /opt && jar xf /tmp/jetty.zip] returned a non-zero code: 1

Probably there is yet another before that line and I suspect, that the wget failed because the version of Jetty declared doesn't exist anymore. But I really don't know why that failed (works for me currently on master).

I will improve the error message, of course.

rhuss avatar Apr 03 '15 08:04 rhuss