Skip to content
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

Closed
knoppiks opened this issue May 13, 2015 · 4 comments
Closed

docker:push - unexpected behavior #165

knoppiks opened this issue May 13, 2015 · 4 comments

Comments

@knoppiks
Copy link

I specified a docker push action on maven deploy with:

<execution>
    <id>push</id>
    <phase>deploy</phase>
    <goals>
        <goal>push</goal>
    </goals>
</execution>

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

[ERROR] Failed to execute goal org.jolokia:docker-maven-plugin:0.11.3:push (push) on project image-name-war: Unable to push image [dreg.private-server.local/image-name] to registry [null] : EOF (Internal Server Error: 500) -> [Help 1]

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.

@rhuss
Copy link
Collaborator

rhuss commented May 13, 2015

Indeed, it should work the same. Could you run your example with -X ? Could you try also to provide a -Ddocker.registry=dreg.private-server.local on the command line (maybe even with an explicite port :5000 appened, too ?)

thanks ...

@jgangemi
Copy link
Collaborator

most likely you are hitting the issue where you need to specify a dummy username/password in the auth config section, see #102.

@rhuss
Copy link
Collaborator

rhuss commented May 13, 2015

BTW, #102 is fixed in the next release 0.11.4 which will be out at the end of this week.

@knoppiks
Copy link
Author

Thanks for the support, the issue was indeed #102.
After adding the empty <authConfig> the push succeeds.

Changing to v0.11.4 won't do the trick somehow, I guess there are other problems with my configuration.

leusonmario pushed a commit to leusonmario/docker-maven-plugin that referenced this issue Aug 18, 2018
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants