-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Can not connect to Ryuk" on macOS with Docker for Mac 2.4.0.0 #3166
Comments
@sazzer Have you found a solution in the meantime? I have the same issue after updating Docker Engine today. Edit: "Downgraded" from Docker Desktop Edge to Docker Desktop Stable and the issue has gone. Looks like a problem in combination with Docker 2.3.6.0. |
For the recent Docker Desktop 2.4.x Release on macOS, see #3159. |
I'm on MacOS 10.14.6 (Mojave). Both TestContainers v1.12.3 and the latest (v1.14.3) have ceased to work with the latest update of Docker that I received today. The exact same symptoms as the OP happen. Version 2.4.0.0 (48506) from the "stable" Channel. Engine is: 19.03.13 Anyone found this and/or have a workaround, short of downgrading/rolling back the version of Docker Desktop (Community)? |
I'm also experiencing the same issue |
This comment has been minimized.
This comment has been minimized.
Docker for Mac 2.4.0.0 was released yesterday, pushing this issue into the stable version. We released 1.15.0-rc2 which includes a fix (#3159) for compatibility - please upgrade. |
No-one has asked me, but I confirm that 1.15.0-rc2 works ;-) |
Same here: 1.15.0-rc2 solves the problem. |
This comment has been minimized.
This comment has been minimized.
I have the same issue. Using 1.15.0-rc2 could be a workaround. It's available in maven central. https://mvnrepository.com/artifact/org.testcontainers/testcontainers/1.15.0-rc2 |
1.15.0-rc2 works for me to. I do have some questions regarding this topic: |
Containers will not terminated. |
This comment has been minimized.
This comment has been minimized.
@tonymurphy please make sure that you're not forcing an old version of |
This comment has been minimized.
This comment has been minimized.
Very soon - we mainly want to get #3102 over the line and into the 1.15.0 final release, as part of mitigation for the upcoming Docker Hub rate limits (#3099)
Ryuk does final cleanup of containers that might have escaped being killed. Testcontainers code tries its best, but in case of a sudden JVM termination or a bug there's a limit to what the Java code can do. Ryuk is external to the JVM process and provides a more surefire method of cleaning up. Having Ryuk enabled is something we strongly recommend. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@vinay-thakkar you can:
|
thanks will try those out. |
@vinay-thakkar The same problem came to me when I updated the docker version. Does this problem occur only for the desktop? |
Not sure about other env. For me it occurred only for 'Docker for Mac'. Our circle CI pipelines are pinned to older versions of Docker so no idea there. And don't have windows machine in team to confirm. |
This comment has been minimized.
This comment has been minimized.
Just an update. Updating to 1.5.0-rc2 solved the issue for me. However running JUnit5 tests in a gradle project from IntelliJ end up in no container being cleaned. |
when using Docker Desktop forMac v2.4.0 there is a problem with Ryuk, see testcontainers/testcontainers-java#3166 It was fixed in Testcontainers v1.15.0-rc2
Docker for Mac 2.4.0.0 introduced a breaking change breaking testcontainers ryuk on MacOS. [Also see the testcontainer issue.](testcontainers/testcontainers-java#3166)
@bsideup you were right, my mistake, sorry for the inconvenience. Thanks! |
This comment has been minimized.
This comment has been minimized.
Worx perfectly |
…id potential failure. See related issue: testcontainers/testcontainers-java#3166
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This issue is about Docker for Mac 2.4.0.0 only. The error message ("can not connect to <...>") itself does not mean that you're having the same issue. Consider creating a new issue if you're having issues with 1.15.0-rc2. For those who are searching for a fix, see this comment: |
One further update: 1.15.0 was released today including the fix (the same as the previous RC builds) |
I've seen this exact error come and go a fair bit on here, but it's just today started happening for me.
I'm using testcontainers-java 1.12.0, but updating to the latest version has no impact at all.
When running my test, I get the following:
And then a seemingly infinite amount of the following:
This is running with Java 1.8.0_222 from Amazon Corretto, running on macOS 10.15.6.
This definitely worked yesterday. I did have an update to the Docker Engine today, and I'm assuming that's relevant, but everything else I'm doing with Docker is all working fine - including a different project that uses the Rust version of TestContainers. (Though I notice that doesn't use Ryuk, which might be relevant)
Cheers
The text was updated successfully, but these errors were encountered: