Error: Could not find a working container runtime strategy

[rudemex]

Expected Behaviour
It is expected to initialize the services of a docker-compose.yml when running tests.

Actual Behaviour
does not initialize the docker container with the service and returns the message “Error: Could not find a working container runtime strategy”.

Testcontainer Logs

testcontainers [INFO] Starting DockerCompose environment "testcontainers-e350456a8ddf"... +0ms
  testcontainers [DEBUG] Checking container runtime strategy "TestcontainersHostStrategy"... +1ms
  testcontainers [DEBUG] Loading ".testcontainers.properties" file... +0ms
  testcontainers [DEBUG] Loaded ".testcontainers.properties" file +4ms
  testcontainers [DEBUG] Found custom configuration: tcHost: "tcp://127.0.0.1:64155", dockerHost: "tcp://127.0.0.1:64155" +0ms
  testcontainers [TRACE] Fetching Docker info... +0ms
  testcontainers [DEBUG] Container runtime strategy "TestcontainersHostStrategy" does not work: "Error: connect ECONNREFUSED 127.0.0.1:64155" +15ms
  testcontainers [DEBUG] Error: connect ECONNREFUSED 127.0.0.1:64155
  testcontainers     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16) +0ms
  testcontainers [DEBUG] Checking container runtime strategy "ConfigurationStrategy"... +0ms
  testcontainers [TRACE] Fetching Docker info... +1ms
  testcontainers [DEBUG] Container runtime strategy "ConfigurationStrategy" does not work: "Error: connect ECONNREFUSED 127.0.0.1:64155" +2ms
  testcontainers [DEBUG] Error: connect ECONNREFUSED 127.0.0.1:64155
  testcontainers     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16) +0ms
  testcontainers [DEBUG] Checking container runtime strategy "UnixSocketStrategy"... +0ms
  testcontainers [TRACE] Fetching Docker info... +0ms
  testcontainers [DEBUG] Container runtime strategy "UnixSocketStrategy" does not work: "AggregateError" +9ms
  testcontainers [DEBUG] AggregateError [ECONNREFUSED]: 
  testcontainers     at internalConnectMultiple (node:net:1122:18)
  testcontainers     at afterConnectMultiple (node:net:1689:7) +0ms
  testcontainers [DEBUG] Checking container runtime strategy "RootlessUnixSocketStrategy"... +0ms
  testcontainers [TRACE] Fetching Docker info... +1ms
  testcontainers [DEBUG] Container runtime strategy "RootlessUnixSocketStrategy" does not work: "AggregateError" +2ms
  testcontainers [DEBUG] AggregateError [ECONNREFUSED]: 
  testcontainers     at internalConnectMultiple (node:net:1122:18)
  testcontainers     at afterConnectMultiple (node:net:1689:7) +0ms
  testcontainers [DEBUG] Checking container runtime strategy "NpipeSocketStrategy"... +0ms
  testcontainers [DEBUG] Container runtime strategy "NpipeSocketStrategy" is not applicable +1ms

Environment Information

• Operating System: macOS Sequoia v15.3.1
• Docker Version: v27.5.1
• Node version: v20.18.2
• Testcontainers version: v10.18.0

[cristianrgreco]

Hi @rudemex, the logs show that Testcontainers could not find a valid container runtime. Why do you think it's an issue with Testcontainers? Are you able to connect to Docker yourself, e.g docker ps? In what mode is Docker running, rootless? Where is the Docker socket on your machine?

[rudemex]

Hi @cristianrgreco , how are you? I have docker desktop working correctly, but I noticed that I need to have testcontainer desktop started to run the tests locally and work correctly, as for the pipelines of gh actions, the initialization of the container through docker-compose was working correctly, but now I return that output and I can't find a way to solve it.

[rudemex]

hi @cristianrgreco, How are you? these days I was checking a little more in depth why I was getting that error, it turns out that the problem does not come from testcontainers, but comes from the Nock library, which is used to mockear http requests, which in my case I use it for several tests.
Searching a little more in depth, they reported this same bug in the Nock repository, now I'm looking for a way to solve it.

nock/nock#2839

Regards