-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
better error message for docker:push if you don't specify -Ddocker.username / -Ddocker.password system properties, autoConfig or have a missing <server><id> value #43
Comments
Yeah, you are right. Going to add this ASAP for the next release. |
just realized this and #102 are related, if not the same thing. |
Still have to verify this, moving it to the 0.11.3 list. |
this still exists but as i said somewhere (#102 i think), i'm not sure how we would know to give a better error message for the docker failure. i think part of the solution could be to check if it's a private repository (not docker hub) and if yes and no auth config is specified, send one w/ using blank strings as the encoded values. the docker cli must do some form of this b/c i can push to private repos w/o any issue. |
With the latest version of Docker/plugin, I get the following error message if authentication fails:
I don't know what happened in the meantime, but I hope that's clear enough ;-) |
BuildMojo - imageTags parameter added to tag an image with additional tags
I was getting quite confused trying to figure out why the push wasn't working. I kept getting the errors shown below.
Turns out adding -Ddocker.username=jolokia -Ddocker.password=jolokia to the CLI fixed it. (Thanks for figuring that out @iocanel!).
I wonder if the plugin could do a big warning if the system properties are not specified and a server id (of the registry host:port) is not available; so new users grok what they need to do.
e.g. if there's no authConfig values and no system properties for docker.username / docker.password and no ~/.m2/settings.xml we should fail the build and output a big warning telling folks to add an authConfig, set the system properties or add something like this to their ~/.m2/settings.xml:
then lots of users who just see this error will thank you ;)
The text was updated successfully, but these errors were encountered: