Timed out waiting for container port to open #4125
Comments
|
Had to downgrade to Docker Desktop |
|
Also seeing this exact issue with testcontainers version |
|
How do you "close" this issue, it keeps happening with random versions of Docker engine and docker desktop. |
|
@schowdiah since the issue is caused by Docker for Windows and not Testcontainers, consider reporting it to the Docker team. We do our best on the Testcontainers side to make things work but some issues (usually related to Docker) are out of our control, unfortunately. |
macbook m1 chip |
|
Yeah. Facing the same issue on RHE. :( |
|
@DJ-Glock can you please try out if it works with the basic example from our reproducer? Also, please follow up in issue #4602, this issue has been closed by the original author and had a different cause. |
|
Noticed this issue happens only if we do |
|
Same issue here. I love this java libraries. ` ` ` ` |
|
Hi there, did you find any fix to this issue? I do not understand how to solve this problem. |
|
I am also still facing this error running,
I have a feeling it might be a Mac specific issue as my teammates don't get this running the same test on Intel machines running Ubuntu. I tried connecting to a remote Docker engine running on an Ubuntu EC2 instance but still get the "timed out waiting for container ports to open" I've also confirmed by running docker ps that the container listens on 1112-1113/tcp, 2112-2113/tcp |
|
I'll reopen it since many folks are complaining |
|
I still have this issue with TestContainers. I am using windows with Docker 24, testcontainers 1.18 version, with cucumber hooks. I have this exception when running : |
|
2023 and still experiencing this same problem with |
|
That's worked for me. |
|
I'm getting this with docker running in an ubuntu container running on docker under ubuntu. This is happening in a test I'm running under gradle. I enabled debug logging and see this: This is especially weird because it says it passed, listing the port, then that it timed out, listing the same port! I've looked at the code of While the wait is going, I'm able to connect using |
|
I did some more testing. I added the causal exception to the log statement, seems the internal port check future gets canceled for some reason. I created my own I'm still stuck trying to get a container based on Then hangs. I tried using the I'm using testcontainers 1.19.3 and openjdk 17.0.9, running in Docker 24.0.7 running in ubuntu 20.04.6 container (build agent), running on docker 20.10.17 ubuntu 22.04.3 (host). It previously worked fine, but I don't remember what I changed to break it. This all works just fine on my M1 mac Temurin/openjdk 17.0.9, docker 24.0.6. |
|
Further debugging: I created a simple app to test with and tested in the build agent this keeps failing in (continued to fail), and then a plain docker-in-docker image published by docker, and it succeeded. I then tried creating a fresh clone of the agent container and it worked. Pulling my hair out, I |
|
Seeing this problem as well Docker version 20.10.22, build 3a2c30b63a Nothing changed in our integration test code and it just stopped working.
|
|
Running into the same problem. Did anyone else on here find a workaround for this ?
I'm using Rancher Desktop version: 1.12.1 |
|
Same issue on Mac M3, Sonoma 14.4, with testcontainer 1.17.2, Colima 0.7.0 for docker and Spring Boot 2.15 + Cucumber. This happens sporadically. Someone pointed out this is not a testcontainer issue but rather a Docker one - so I am looking for a workaround. |
#3923 is still reproducible with
com.playtika.testcontainers:embedded-keycloak:2.0.8even after forcibly upgradeorg.testcontainers:testcontainerstransitive dependency to1.15.3, gettingDocker For Windows
3.3.3The text was updated successfully, but these errors were encountered: