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
How to actually get verbose output from docker:build? #1760
Comments
@davidmichaelkarr : You should be able to see fully qualified image name when you do a
In above case image name is If you specify
If you specify
|
I'm getting nothing from all those variations. I think this must mean that the plugin is finding nothing to do. I don't know why that would be, but I would have to guess that it's not seeing a Dockerfile. Would the plugin print no output if that happened? We'll look closely at the config later today. |
@davidmichaelkarr : I'm not able to see any image configuration in your plugin configuration. Could you please try adding this in plugin configuration? <images>
<image>
<name>your-registry.org/yourusername/yourimagename:tag</name>
<build>
<dockerFile>Dockerfile</dockerFile>
</build>
</image>
</images> By default plugin would automatically detect Could you please check our dockerfile sample project to see how it's different from your project? |
OK. Would this look better (untested)?
|
It should work given your Dockerfile has correct references as per your configured docker context directory. |
It looks like the name can't have the tag, so we're adding a tags block. |
default tag is added after
|
Well, we we were trying to have "yourtag" reference a property, like "${docker.image.tag}". That gets a syntax error. Fortunately, we are were able to do this with a tags block. |
We are using v0.44 of docker-maven-plugin. I was working on this a few days ago, and I saw that we were getting verbose output, where it would show what tag was being applied to the image, but for some reason we get almost nothing in the output. I've set "verbose=true" several different ways now, and it doesn't make any difference.
Our current plugin block looks like this:
When the build runs, we get almost nothing as I said, just this:
The text was updated successfully, but these errors were encountered: