-
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
docker:push - unexpected behavior #165
Comments
Indeed, it should work the same. Could you run your example with -X ? Could you try also to provide a thanks ... |
most likely you are hitting the issue where you need to specify a dummy username/password in the auth config section, see #102. |
BTW, #102 is fixed in the next release 0.11.4 which will be out at the end of this week. |
Thanks for the support, the issue was indeed #102. Changing to v0.11.4 won't do the trick somehow, I guess there are other problems with my configuration. |
Remove the pinning of Guava to version 14.0.1 to fix spotify/docker-maven-plugin#165. Guava was held to 14.0.1 before because a combination of Plexus/Guice code used or invoked by the maven plugin testing harness called methods in Guava that have been removed after version (specifically `MapMaker.makeComputingMap). The main fix to remove that need is to avoid using that part of the testing harness altogether by stubbing out the `MavenProject` instance instead of trying to look it up in the Plexus container. Fixes fabric8io#165.
I specified a docker push action on maven deploy with:
For the image
<name>dreg.private-server.local/image-name</name>
.I executed a docker push with
docker push dreg.private-server.local/image-name
which succeeded.But the maven execution fails with
Maybe I'm wrong but I expected the maven goal to do exactly the same command I issued by hand, as I defined the name of the image with a registry prefix.
The text was updated successfully, but these errors were encountered: