wait for port doesn't work on Windows
See original GitHub issueWait for port doesn’t work on Windows.
As an example:
<ports>
<port>3336:3306</port>
</ports>
<wait>
<tcp>
<ports>
<port>3306</port>
</ports>
</tcp>
<time>40000</time>
</wait>
This won’t work, while the following works and maven plugin connects to mysql using jdbc:mysql://localhost:3336
<wait>
<time>10000</time>
</wait>
Maven: 3.3.9 docker-maven-plugin: 0.15.16 Windows 10
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:17 (1 by maintainers)
Top Results From Across the Web
TCP/IP port exhaustion troubleshooting - Windows Client
Learn how to troubleshoot port exhaustion issues. Port exhaustion occurs when all the ports on a machine are used.
Read more >How to Fix Port in Use Error in Windows 11/10 - Techbout
To fix "Port in use, please wait" error message in Windows 10, open Printer properties and make sure that correct Port type is...
Read more >Printer port in use please wait Error in Windows 10
Printer port in use please wait Error in Windows 10 · Open Settings · Select Update and Security · Select Troubleshoot · Select...
Read more >How to Fix Port in Use, Please Wait – Printer Error Message in ...
The Printer Troubleshooter is the first step in resolving the "Port in use, please wait" error. Most print problems can be resolved using...
Read more >Port in use, please wait - Printer error message in Windows 11 ...
However, the printer continues to print wirelessly from phones. This suggests there's some problem existing between the printer and the computer ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The configuration at branch “working” of my sample project now works with docker-maven-plugin v0.23.0 and boot2docker v18.01.0-ce on Windows 7 64-bit.
In short, it uses
mapped
mode port configurations:I think I’m seeing the same problem on a Mac using
docker-machine
. I specify:(Ports are allocated by the
build-helper-maven-plugin
earlier in the POM)0.27.2
10.11.6
17.10.0-ce, build f4ffd25
version 0.13.0, build 9ba6da9
When I run
mvn clean verify -X -e
(in thenotification-integration
module containing the MDP plugin configuration) I get the errors:[ERROR] DOCKER> Error occurred during container startup, shutting down...
Cannot watch on port 61334, since there is no network binding
The ports are properly mapped according to the debug output below:
If I use a simple
<wait><time>15000</time></wait>
the Maven build succeeds (MDP starts containers, integration tests run successfully for my project, etc.)The relavent output: