terminating test containers makes all container unreachable

[zYasser]

Expected Behaviour
Tests should be able to connect to the database container normally after startup.
...

Actual Behaviour
After terminating a test run using Ctrl+C, all subsequent tests fail because the database container becomes unreachable. Although the container is still visible in Docker, it along with all other running containers becomes completely inaccessible. The only workaround is to restart Docker entirely.
...

Testcontainer Logs
...

Steps to Reproduce

1. Run tests using Jest.

2. Start a PostgreSQL container with the following setup: const container = await new PostgreSqlContainer(image) .withDatabase(database) .withUsername(username) .withPassword(password) .withExposedPorts(5432).withWaitStrategy(Wait.forLogMessage('database system is ready to accept connections', 1)) .start()

3. While the tests are running, press Ctrl+C to forcibly terminate the process.

4. Re-run the tests. They now fail, and all Docker containers become unreachable.

Environment Information

• Operating System:Windows 10
• Docker Version:Docker version 26.1.1, build 4cf5afa
• Node version:v20.15.0
• Testcontainers version:11.0.3

[cristianrgreco]

I don't really understand.

Re-run the tests. They now fail, and all Docker containers become unreachable.

What's the failure?

And are you saying that all running containers which were not created by Testcontainers are now unreachable, because if so that seems an issue with the OS/Docker.

[zYasser]

The problem occurs when I re-run the tests: the containers are created successfully and everything looks fine, but they simply can't accept any connections not just the ones created by Testcontainers, but all containers become unreachable.

This only happens if the containers weren't properly removed after the previous test run. If I gracefully shut down the tests and stop the containers, everything works fine ,I can re-run the tests multiple times without any issues.

However, if the program is terminated (e.g., with Ctrl+C), Jest is unable to shut everything down cleanly, and this leads to the problem.

[zYasser]

it seems it is OS problem

[zYasser]

If anyone faces this problem in the future, the fix is to use the withReuse() option.
This option prevents Testcontainers from recreating the containers. You may ask, why is that important?
The issue is that deleting and recreating containers too quickly can mess up the network interfaces in WSL2/Hyper-V for some reason.
By default, Testcontainers will delete any existing containers it created and then recreate them.
To avoid this cycle of deletion and recreation and the potential network issues you should reuse the existing container by enabling withReuse().