-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 at localhost #892
Comments
Probably related, you are right. |
Right. so far I am only using a global postgres container(https://www.testcontainers.org/usage/database_containers.html#jdbc-url) in my integration test. |
I am running into the same issue while building my project in BitBucket pipelines. I can see that the Docker environment is detected during startup with the following message in the logs:
However, later on I get the same error as @fang10 (notice the port number is also 32768)
|
I am using latest release (1.9.1) also..
|
As of this afternoon (AEST), testcontainers:localstack is again not working in BitBucket pipelines. The error is the same as before:
|
@alex-arana @fang10 I'm unsure if this a general incompatibility with Testcontainers, or just something that's rolled out for some Bitbucket users. |
This is caused by the following bug within test containers. The reason why we enabled this feature Is described here: For now you can reach out to Atlassian support so we can add you to an exclusion list whilst test containers fixes this issue. I'll comment again on the 712, as over the coming months, we will be removing the exclusion list as it leaves potential security holes in our product, and if test containers hasn't fixed this issue by than it will render it unusable. |
Related ticket at Atlassian. |
It seems to me that the ResourceReaper implementation always tries to bind mount the docker unix socket when starting ryuk. This will fail in environments where only the tcp socket is available. testcontainers-java/core/src/main/java/org/testcontainers/utility/ResourceReaper.java Lines 72 to 84 in 58a6c69
|
I am running into the same issue while building my project in BitBucket pipelines. Are there any updates regarding this issue? |
I faced with this issue at version 1.8.3 although it worked in the past and no firewall constrain.
Hope it help. |
We're aware of this issue, however, I'll have to close this as a duplicate of #700. Please follow that ticket for more updates. |
I am running into an issue using testcontainer with bitbucket pipeline. The issue may be relevant to recent bitbuket pipeline changes (e.g. #700) since I didn't have this problem a few days ago.
The text was updated successfully, but these errors were encountered: