Plugin doesn't work on Windows - wrong path handling about docker-maven-plugin

[arghya88]

remove targetPath tag

[BrettFieber]

In case you can't wait for that PR, here is a workaround I came up with:

<!-- define a default value in <properties> ->
<properties>
    ...
    <docker.resource.targetPath>/</docker.resource.targetPath>
</properties>

<!-- define a profile that is activated in windows environments -->
<profiles>
    <profile>
        <id>windows</id>
        <activation>
            <os>
                <family>Windows</family>
            </os>
        </activation>
        <properties>
            <docker.resource.targetPath></docker.resource.targetPath>
        </properties>
    </profile>
</profiles>

<!-- then set the targetPath using the property -->
<build>
    <plugins>
        <plugin>
                <groupId>com.spotify</groupId>
                <artifactId>docker-maven-plugin</artifactId>
                <version>0.2.12</version>
                <configuration>
                    <imageName>${docker.image.prefix}/${project.artifactId}</imageName>
                    <dockerDirectory>src/main/docker</dockerDirectory>
                    <resources>
                       <resource>
                           <targetPath>${docker.resource.targetPath}</targetPath>
                           <directory>${project.build.directory}</directory>
                           <include>${project.build.finalName}.jar</include>
 ...

Hope this helps.

[sunieldalal]

I was facing the same issue. Upgraded to 0.3.9 version and no longer facing the issue.

[chrisdostert]

@arghya88 your suggestion worked great for me

[rharido]

If you want to copy your resources to a specific folder in the docker image you will need targetPath. In this case it is still a problem.
/opt/${project.artifactId} -- Fails in windows

[rohansingh]

What happens if you use backslashes in the targetPath?

[sellersj]

I'm running into this issue too on version 0.2.11. I've tried:
/
${file.separator}
/
/

//

Any helpers or work arounds would be great.

[sellersj]

I have not tested it yet, but it looks like someone has made a fix. It's waiting in a PR
https://github.com/oberthur/docker-maven-plugin/commit/1f303e0aeb76aee5122d6d7bda4cd240518a6337

[sellersj]

I've now tested oberthur's fork and it works for me on windows. The change is in #65

[pmandayam]

@BrettFieber this worked for me, thanks

[davidxia]

This should be resolved by https://github.com/spotify/docker-maven-plugin/pull/121/commits

[javacody]

I just tried this with 0.3.5 on Windows. It's still broken.

[sellersj]

Not that it helps for the spotify plugin, but one I've found that works on windows is https://github.com/rhuss/docker-maven-plugin

Good luck.

[rohansingh]

Reopening this based on reports that it doesn't work. We welcome PR's but are unlikely to fix this at Spotify, since nobody has a Windows setup to test it out with.

[craykg]

I ran into this same issue, and have created a PR that works around the issue (its actually a bug in the Windows implementation of Paths.get)

[mattnworb]

@javacody do you still have issues with 0.3.9-SNAPSHOT? If so can you tell us the output of running your maven commands with the -e flag?

[mattnworb]

@sunieldalal thanks for the confirmation!