I stumbled upon moby/moby#42442 which periodically breaks tests that are based on testcontainers-hs.
One way to workaround this issue is to disable IPv6 altogether on the machine that runs tests, but IMO this doesn't sound like a nice solution since test suite results consistency will depend on local setup.
Instead, it'd be better to run the ryuk container with --publish 127.0.0.1::8080 instead of --publish 8080, however, this is not viable with the current interface provided by testcontainers-hs.
What I propose to do is to add a version of withContainers function that will allow running the TestContainer action either with custom Config or with custom Reaper container.
I stumbled upon moby/moby#42442 which periodically breaks tests that are based on
testcontainers-hs.One way to workaround this issue is to disable IPv6 altogether on the machine that runs tests, but IMO this doesn't sound like a nice solution since test suite results consistency will depend on local setup.
Instead, it'd be better to run the
ryukcontainer with--publish 127.0.0.1::8080instead of--publish 8080, however, this is not viable with the current interface provided bytestcontainers-hs.What I propose to do is to add a version of
withContainersfunction that will allow running theTestContaineraction either with customConfigor with custom Reaper container.