Could not find a working container runtime strategy

[ahmed-deftoner]

Expected Behaviour
Postgres Container should start

Actual Behaviour
Postgres Container did not start

Testcontainer Logs
Error: Jest: Got error running globalSetup - C:\Users\carbo\Projects\twin-premium-api\Tests\Integration\setup.ts, reason: Could not find a working container runtime strategy
at getContainerRuntimeClient (C:\Users\carbo\Projects\twin-premium-api\node_modules\testcontainers\build\container-runtime\clients\client.js:64:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async PostgreSqlContainer.start (C:\Users\carbo\Projects\twin-premium-api\node_modules\testcontainers\build\generic-container\generic-container.js:54:24)
at async PostgreSqlContainer.start (C:\Users\carbo\Projects\twin-premium-api\node_modules@testcontainers\postgresql\build\postgresql-container.js:34:47)
at async initPostgres (C:\Users\carbo\Projects\twin-premium-api\Tests\Integration\setup.ts:12:22)
at async Promise.all (index 0)
at async init (C:\Users\carbo\Projects\twin-premium-api\Tests\Integration\setup.ts:7:5)
at async C:\Users\carbo\Projects\twin-premium-api\node_modules@jest\core\build\runGlobalHook.js:109:13
at async waitForPromiseWithCleanup (C:\Users\carbo\Projects\twin-premium-api\node_modules@jest\transform\build\ScriptTransformer.js:160:5)
at async ScriptTransformer.requireAndTranspileModule (C:\Users\carbo\Projects\twin-premium-api\node_modules@jest\transform\build\ScriptTransformer.js:808:16)

Steps to Reproduce

1. Windows but ran tests in WSL2
2. Docker version 24.0.7 and NodeJS version v20.12.1
3. npx jest --config ./src/Tests/Integration/it.jest.json src/Tests/Integration/Agency/agency.it.spec.ts
4. Error: Jest: Got error running globalSetup - C:\Users\carbo\Projects\twin-premium-api\Tests\Integration\setup.ts, reason: Could not find a working container runtime strategy

Environment Information

• Operating System: Windows Subsystem For Linux
• Docker Version: 24.0.7
• Node version: v20.12.1
• Testcontainers version: ^10.9.0

[ericvoshall]

Are you using MSW? I had an issue where MSW was swallowing requests to Docker to create test containers.

[kiview]

What is MSW?

Did you execute the tests as a WSL process? This path here C:\Users\carbo\Projects\twin-premium-api\Tests\Integration\setup.ts, reason: Could not find a working container runtime strategy looks like a Windows process, there will not be an OOTB integration between the Windows host and Docker within WSL if Docker Desktop is not used.

[ericvoshall]

MSW is a testing tool. There’s a related issue on their repo here.

[ahmed-deftoner]

What is MSW?

Did you execute the tests as a WSL process? This path here C:\Users\carbo\Projects\twin-premium-api\Tests\Integration\setup.ts, reason: Could not find a working container runtime strategy looks like a Windows process, there will not be an OOTB integration between the Windows host and Docker within WSL if Docker Desktop is not used.

I run docker on WSL, and I executed all the commands on WSL and not Windows, but you're right, the path seems different, I'll verify it again though