Skip to content
This repository has been archived by the owner on Mar 21, 2022. It is now read-only.

Better feedback on error #119

Closed
ggtools opened this issue Aug 3, 2015 · 5 comments
Closed

Better feedback on error #119

ggtools opened this issue Aug 3, 2015 · 5 comments

Comments

@ggtools
Copy link

ggtools commented Aug 3, 2015

I recently had an issue creating an image using the docker-maven-plugin. It was simply that the Dockerfile was not copied to the working directory but it only happened on the CI server. My problem here is that the feedback I got from Maven was not really useful at all:

[INFO] Building image evollis/middle-business:049daf7
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[CUT]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19.905 s
[INFO] Finished at: 2015-07-31T17:13:45+00:00
[INFO] Final Memory: 91M/1164M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.spotify:docker-maven-plugin:0.2.12:build (docker-image-create) on project xxx: Exception caught: Request error: POST unix://localhost:80/build?t=evollis/middle-business:049daf7: 500: HTTP 500 Internal Server Error -> [Help 1]

I don't know if it is possible to get more feedback from the docker daemon but that'll have been great to get the underlying error message

@tatsuya
Copy link

tatsuya commented Sep 16, 2015

+1

1 similar comment
@ghiron
Copy link

ghiron commented Oct 14, 2015

+1

@MarkNBroadhead
Copy link

MarkNBroadhead commented Jul 11, 2016

+1 Having an issue right now and troubleshooting is difficult without more visibility. It appears more specific error messages are returned in the body of the error. Is there any way this information can be returned in the stack trace?

@fc572
Copy link

fc572 commented Feb 1, 2017

I have had the same issue. This happens because Docker build process doesn't like upper case letters in the image name.
Change the artifact id in your pom file to have all lowercase letters.

@davidxia
Copy link
Contributor

This looks like a duplicate of this issue. Closing this one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants