Expose extra volumes on build after runCmds

[alethenorio]

I am trying to export a few different paths in a volume container built by the plugin by setting up the assembly with all the files I need and then trying to run commands using runCmds tag to move files into folder which I expose as volumes using the tag.

This does not seem to work as I get empty directories in the folders I exposed as volumes. I believe this has to do with the fact that the copy command happens after all volumes have been exposed

It's stated clearly in the Dockerile VOLUME documentation

Note: If any build steps change the data within the volume after it has been declared, those changes will be discarded.

Wouldn't it be better to export extra volumes after all runCmds have run?

[rhuss]

Missed that, thanks for pointing that out. Moved it now to the end of the Dockerfile, this will be available in 0.13.7, to be released this week ...

[alethenorio]

Wow, that was quick.
Awesome. I originally meant the bug report for the volumes tag but I
realise even the assembly tag created volume can probably be moved to the
end as well, keeping all volumes at the same place.

Looking forward to the release.

On Mon, 30 Nov 2015, 22:35 Roland Huß notifications@github.com wrote:

Missed that, thanks for pointing that out. Moved it now to the end of the
Dockerfile, this will be available in 0.13.7, to be released this week ...

—
Reply to this email directly or view it on GitHub
https://github.com/rhuss/docker-maven-plugin/issues/341#issuecomment-160768979
.

[rhuss]

Well, it's not always that fast ;-) (but currently I'm working on a release anyway :)