Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

docker:start always blocks on windows

See original GitHub issue

Description

Whenever I use docker:start on windows it’s always blocking build execution although docker container was successfully started and wait condition satisfied.

I’m using the latest plugin version. I tried explicitly specify docker.follow=false - didn’t help. The same config works fine with docker for OSX.

Info

d-m-p version : 0.27.1
Maven version (mvn -v) : 3.5.4
Docker version : 18.06.1-ce-win73
If it’s a bug, how to reproduce : My docker execution config looks like this:

            <plugin>
                <groupId>io.fabric8</groupId>
                <artifactId>docker-maven-plugin</artifactId>
                <version>0.27.1</version>
                <configuration>
                    <images>
                        <image>
                            <name>localstack/localstack:0.8.7</name>
                            <run>
                                <env>
                                    <SERVICES>dynamodb</SERVICES>
                                </env>
                                <ports>
                                    <port>4569:4569</port>
                                </ports>
                                <log/>
                                <wait>
                                    <log>^Ready\.$</log>
                                </wait>
                            </run>
                        </image>
                    </images>
                    <skip>${skipTests}</skip>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>start</goal>
                            <goal>stop</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

then execution docker:start -X will show that waitcondition was met, execution returned 0 and then process hangs.

Issue Analytics

State:
Created 5 years ago
Comments:25 (8 by maintainers)

Top GitHub Comments

1reaction

nceleriercommented, Jun 29, 2021

Yes, I have just created the merge request.

1reaction

rohanKanojiacommented, Jun 27, 2021

I’ve released 0.36.1 with @ncelerier 's fix.

@SimY4 @jeacott1 @ebouvi01: Could you please help us out by trying out 0.36.1 on windows and providing feedback on whether this issue is resolved or not whenever you have some time? If it’s working we can go ahead and close this.

Top Results From Across the Web

Start containers automatically - Docker Documentation

The following example starts a Redis container and configures it to always restart unless it is explicitly stopped or Docker is restarted.

Ensuring Containers Are Always Running with Docker's ...

In today's article we will discuss how to use Docker's restart policy to automatically restart containers and avoid those late-night ...

Docker container will automatically stop after "docker run -d"

The centos dockerfile has a default command bash . That means, when run in background ( -d ), the shell exits immediately. Update...

Install Docker on Windows (WSL) without Docker Desktop

If configured as above, I recommend always running docker from wsl. Do you want to run a container? Do so from a WSL...

Containers — Docker SDK for Python 6.0.1 documentation

blkio_weight_device – Block IO weight (relative device weight) in the form ... cpu_percent (int) – Usable percentage of the available CPUs (Windows only)....