You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the logs, it seems Ryuk dies before the next container is started. Could you try enabling the verbose mode in Ryuk and trying to capture Ryuk logs and see if the connections are happening?
Testcontainers version
0.30.0
Using the latest Testcontainers version?
Yes
Host OS
Windows 11
Host arch
amd64
Go version
1.21.6
Docker version
$ docker version Client: Cloud integration: v1.0.35+desktop.11 Version: 25.0.3 API version: 1.44 Go version: go1.21.6 Git commit: 4debf41 Built: Tue Feb 6 21:13:02 2024 OS/Arch: windows/amd64 Context: default Server: Docker Desktop 4.28.0 (139021) Engine: Version: 25.0.3 API version: 1.44 (minimum version 1.24) Go version: go1.21.6 Git commit: f417435 Built: Tue Feb 6 21:14:25 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.28 GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb runc: Version: 1.1.12 GitCommit: v1.1.12-0-g51d5e94 docker-init: Version: 0.19.0 GitCommit: de40ad0
Docker info
What happened?
I ran an integration test that spins up a PostgreSQL database which usually works without any issue on other systems. But on this machine it says:
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: