-
Notifications
You must be signed in to change notification settings - Fork 283
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
Bug: Testcontainers in Docker container #644
Comments
am planning on fixing in #622 |
This should also come with documentation on how to setup a working CI pipeline on Gitlab and Github. |
Git hub is easy, it does not require dind
…On Tue, Jul 16, 2024, 7:05 PM Thomas Lutz ***@***.***> wrote:
This should also come with documentation on how to setup a working CI
pipeline on Gitlab and Github.
—
Reply to this email directly, view it on GitHub
<#644 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACECGJA33YMVZKRT54KPA5TZMWRLDAVCNFSM6AAAAABKUPDO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZRHE2TQNJRGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
We were impacted by this as well, costed us almost 2 days 👎 |
@alexanderankin We are not using "dind" on a private hosted GitLab/Runner and it still doesnt work. Our runner does run in Docker, with "host" network and "/var/run/docker.sock" access. This used to work fine in v3.x hasnt work since 4.x. I'm also using testcontainers-go, and that one works fine, it's something with this package. |
For me, it works like this (in a Gitlab Runner):
|
This workaround worked for us in github runner (it works well with ryuk being enabled):
|
As @asafm reported in Slack, starting the container in Docker-Wormhole-Pattern mode with host network seems to work:
|
method get_container_host_ip(self) in testcontainers/core/container.py
have the following code commented (you drive me crazy) and should be uncommented
The text was updated successfully, but these errors were encountered: