docker stop does not work

Hello,

I have a maven project and the docker plug in configuration for it is listed below. Starting works fine. But after the integration tests are done and the plug in shuts down the container it just hangs with this output forever

[INFO] — docker-maven-plugin:0.14.1:stop (stop) @ wh-cdc-web — 08:52:37.421 DB> 2016-09-06 06:52:37 UTC [1-2] LOG: received smart shutdown request 08:52:37.421 DB> 2016-09-06 06:52:37 UTC [10-2] LOG: autovacuum launcher shutting down

The container is not running anymore so it was shutdown, it’s just the plugin waiting for something.

PlugIn Version: 0.15.16 Docker version 1.12.1, build 23cf638

Dockerfile.txt

<plugin>
                <groupId>io.fabric8</groupId>
                <artifactId>docker-maven-plugin</artifactId>
                <version>${docker.maven.plugin.fabric8.version}</version>
                <configuration>
                    <logDate>default</logDate>
                    <autoPull>true</autoPull>
                    <images>
                        <image>
                            <alias>db</alias>
                            <name>postgres:9</name>
                            <build>
                                <ports>
                                    <port>5432</port>
                                </ports>
                                <dockerFileDir>${project.basedir}/docker</dockerFileDir>
                            </build>
                            <run>
                                <ports>
                                    <port>${dbPort}:5432</port>
                                </ports>
                                <wait>
                                    <log>database system is ready to accept connections</log>
                                    <time>20000</time>
                                </wait>
                                <log>
                                    <prefix>DB</prefix>
                                    <color>yellow</color>
                                </log>
                            </run>
                        </image>
                    </images>
                </configuration>

                <!-- Hooking into the lifecycle -->
                <executions>
                    <execution>

                        <id>start</id>
                        <phase>pre-integration-test</phase>
                        <goals>
                            <goal>build</goal>
                            <goal>start</goal>
                        </goals>
                    </execution>
                    <execution>
                        <id>stop</id>
                        <phase>post-integration-test</phase>
                        <goals>
                            <goal>stop</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

[rhuss]

Thanks ! I will try to reproduce this on a virtual box image and can hopefully trigger the same bug.

[rhuss]

@andreasaronsson I tried jnr-unixsocket-0.19 already but I got tons of issues with closed streams. Not sure that’s d-m-p doing something wrong or the lib. Going to investigate this further, as it seems that it contains some fix which could be related to this issue.