I encounter the same problem. Did you find a solution?

Under windows, there's a check that has to be set, the Expose daemon on tcp://localhost:2375 without LTS. I have checked it and I was able to run once the build, successfully - and an image was built - but after another run (mvn package) I started having that error. Tried restarting everything with no success.

Output of docker version:
Client:
Version: 17.09.0-ce
API version: 1.32
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:40:09 2017
OS/Arch: windows/amd64

Server:
Version: 17.09.0-ce
API version: 1.32 (minimum version 1.12)
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:45:38 2017
OS/Arch: linux/amd64
Experimental: true

The error message in the original issue indicates that the docker daemon is not listening at the address the plugin is trying to communicate with it at. See the “Setup” section of the readme for how you can customize the address to reach docker at.

echo %DOCKER_HOST%
tcp://localhost:2375

During the build i get this:
[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.3.6:build (default) on project AAAa: Execution default of goal com.spotify:dockerfile-maven-plugin:1.3.6:build failed: Illegal char <:> at index 3: tcp://localhost:2375 -> [Help 1]

I solved the problem by using the new plugin dockerfile-maven. Was not the deamon as previously mentioned but the plugin.

For me the issue was Capital letter in image name while building the Image .
For example following plugin configuration was giving me error .

<plugin>
           <groupId>com.spotify</groupId>
           <artifactId>dockerfile-maven-plugin</artifactId>
           <version>1.3.6</version>
           <configuration>
           <useConfigFile>false</useConfigFile>
           <useMavenSettingsForAuth>true</useMavenSettingsForAuth>	
               <repository>${docker.image.prefix}/dockerAgent</repository>
           <buildArgs>
   	<JAR_FILE>target/${project.build.finalName}.jar</JAR_FILE>
   		</buildArgs>
           </configuration>
   <executions>
   <execution>
   	<id>default</id>
   	<phase>install</phase>
   	<goals>
   		<goal>build</goal>
   	</goals>
   </execution>
   </executions>
       </plugin> 

The Issue got resolved by changing the "dockerAgent" to dockeragent (all letters in small cases).

I had the same issue running Docker and Maven on Windows. My configuration tag was

${docker.image.prefix}/${project.artifactId}
...

And the ${project.artifactId} resolved to a name that had capital letters.
This led to the error "Cannot retry request with a non-repeatable request entity: Connection reset by peer: socket write error -> [Help 1]".

Changing the docker image to lowercase fixed it.

Thanks abhisheknn

For me the issue was an extra / in the name. My configuration was ${docker.image.prefix}/${project.artifactId}, and the prefix itself already had a /.

set class path //设置环境变量
DOCKER_HOST=unix:///var/run/docker.sock
or add args before CMD //或者增加启动参数
DOCKER_HOST=unix:///var/run/docker.sock mvn clean install docker:build

For me the issue was Capital letter in image name while building the Image .
For example following plugin configuration was giving me error .

<plugin>
           <groupId>com.spotify</groupId>
           <artifactId>dockerfile-maven-plugin</artifactId>
           <version>1.3.6</version>
           <configuration>
           <useConfigFile>false</useConfigFile>
           <useMavenSettingsForAuth>true</useMavenSettingsForAuth>	
               <repository>${docker.image.prefix}/dockerAgent</repository>
           <buildArgs>
   	<JAR_FILE>target/${project.build.finalName}.jar</JAR_FILE>
   		</buildArgs>
           </configuration>
   <executions>
   <execution>
   	<id>default</id>
   	<phase>install</phase>
   	<goals>
   		<goal>build</goal>
   	</goals>
   </execution>
   </executions>
       </plugin> 

The Issue got resolved by changing the "dockerAgent" to dockeragent (all letters in small cases).

It worked for me as well. Thanks a ton :)

For me the issue was Capital letter in image name while building the Image .

Issue got resolved by changing the upper case to smaller case on the artifact id which is used for the docker image name. Thanks

I believe this issue should re-opened, there is totally no error message that indicates a problem with uppercase / lowercase. This should be fixed in the plugin.

I had the same issue running Docker and Maven on Windows. My configuration tag was

${docker.image.prefix}/${project.artifactId}
...

And the ${project.artifactId} resolved to a name that had capital letters.
This led to the error "Cannot retry request with a non-repeatable request entity: Connection reset by peer: socket write error -> [Help 1]".

Changing the docker image to lowercase fixed it.

Thanks abhisheknn

This fixed it for me. seems to be an issue with the plugin

I can confirm that changing the repository-name to my own value (instead of project.artifactId) fixed this. The ${project.groupId}/${project.artifactId} has upper-case chars.

<plugin>
  <groupId>com.spotify</groupId
  <artifactId>dockerfile-maven-plugin</artifactId>
  <version>1.4.10</version>
...
  <configuration>
    <repository>${project.groupId}/${project.artifactId}</repository>
    <tag>${project.version}</tag>
  </configuration>
</plugin>

to

<plugin>
  <groupId>com.spotify</groupId
  <artifactId>dockerfile-maven-plugin</artifactId>
  <version>1.4.10</version>
...
  <configuration>
    <repository>domain/my_project_name</repository>
    <tag>${project.version}</tag>
  </configuration>
</plugin>

For me the issue was Capital letter in image name while building the Image .
For example following plugin configuration was giving me error .

<plugin>
           <groupId>com.spotify</groupId>
           <artifactId>dockerfile-maven-plugin</artifactId>
           <version>1.3.6</version>
           <configuration>
           <useConfigFile>false</useConfigFile>
           <useMavenSettingsForAuth>true</useMavenSettingsForAuth>	
               <repository>${docker.image.prefix}/dockerAgent</repository>
           <buildArgs>
   	<JAR_FILE>target/${project.build.finalName}.jar</JAR_FILE>
   		</buildArgs>
           </configuration>
   <executions>
   <execution>
   	<id>default</id>
   	<phase>install</phase>
   	<goals>
   		<goal>build</goal>
   	</goals>
   </execution>
   </executions>
       </plugin> 

The Issue got resolved by changing the "dockerAgent" to dockeragent (all letters in small cases).

It worked for me as well. Thanks a ton :)

This solved the issue.Thanks.

Don't understand why we don't think such issues are a serious thread to open-source in contemporary software.

Work for me. It is very simple issue. check name of your project.
I have name in Uppercase like this name = Xyz. I change to lower case and every thing work fine. ${project.name} = xyz . Thank you all

I too had the same problem
We need not remove the capital cases I belive

dockerfile plug in uses project version
my pom.xml was having 0.0.1-SNAPSHOT and i changed it to 0.0.1.SNAPSHOT and images built succesfully