Docker Maven Spotify Plugin - Ability to switch to insecure registry

Question

I use the Spotify Maven plugin to automate the construction and deployment of docker images for certain maven goals.

However, I am running a private, unsecured registry, accessible through the following node: server.mydomain.com►000. However, it seems like I can’t get the plugin to block a secure push file in the repository? It uses https://server.mydomain.com//000 .

Is there a way to make the plugin not use https?

Thanks.

Edit:

POM configuration of the current plugin:

<plugin> <groupId>com.spotify</groupId> <artifactId>docker-maven-plugin</artifactId> <version>0.4.3</version> <configuration> <imageName>server.mydomain.com:5000/${project.artifactId}</imageName> <baseImage>java</baseImage> <entryPoint>["java", "-jar", "/${project.build.finalName}-packaged.jar"]</entryPoint> <resources> <resource> <targetPath>/</targetPath> <directory>${project.build.directory}</directory> <include>${project.build.finalName}-packaged.jar</include> </resource> </resources> <imageTags> <imageTag>${project.version}</imageTag> <imageTag>latest</imageTag> </imageTags> <retryPushCount>0</retryPushCount> </configuration> <executions> <execution> <id>build-image</id> <phase>package</phase> <goals> <goal>build</goal> </goals> </execution> <execution> <id>push-image</id> <phase>deploy</phase> <goals> <goal>push</goal> </goals> </execution> </executions> </plugin> 

Answer 1

This is similar to Docker behavior and is not related to the maven plugin you are using, see this Docker question which mentions the need to install --insecure-registry http://server.mydomain.com:5000 when starting the Docker daemon.