Closed stevenh closed 1 week ago
PR is now open against moby-ryuk which fixes the underlying issue which is that the reaper container doesn't reset it's waiting for connection timeout, which means it will randomly shutdown while in use if its connection count ever reaches zero.
Once that's merged and a new release made, we'll need to PR to bump the container image version.
Testing locally I can now run 100 iterations without fail, where as previously 10 was usually enough to trigger an issue.
go test -run=TestGenericReusableContainerInSubprocess -count=100 -v -failfast
Super deep investigation, thanks for doing this!
No problem @mdelapenya just been tripping over issues trying to get a clean test run, so now have a few PR's in flight.
Looks like someone authorised the test run which has now passed, don't suppose you have the power to do a merge and release so I can get the image PR done do you as this is going to be causing all sorts of issues so would be good to get it in?
Should we re-open until we have a release and PR to bump the container version?
Reopening until the next release of Ryuk, which will solve this issue
@mdelapenya not sure if you intended to close this with the PR against a fork of moby-ryuk?
@mdelapenya not sure if you intended to close this with the PR against a fork of moby-ryuk?
Oh my! I pushed to my origin right after updating ryuk and it seems it triggered the auto-close. Reopening 🤦
For those seeing this try cloning the moby-ryuk repo and running the following in it to replace the image that testcontainers-go uses to see if it does fix:
docker build -f linux/Dockerfile -t testcontainers/ryuk:0.7.0 .
Given ryuk:0.8.1 was released, and the main branch comes with it, I think we can close this one.
Please reopen if you consider it's not fixed, thanks!
Testcontainers version
fe0d3a835bfc3183c569457a0a166f496ccbb900
Using the latest Testcontainers version?
Yes
Host OS
Linux
Host arch
amd64
Go version
1.22
Docker version
Docker info
What happened?
Running TestGenericReusableContainerInSubprocess randomly fails.
Relevant log output
Additional information
This is a bug in the reaper, PR incoming.