You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to execute some integration tests using a docker-compose file that I'm passing it to the FluentDocker.
Locally (windows machine) it works ok because (I assume) I already have the docker running, so the FluentDocker knows how to connect to it.
In my case, I'm running a dind, so the tests are in one pod, and the docker is on another pod,
I'm getting this error: Ductus.FluentDocker.Common.FluentDockerException : Failed to find docker client binary - please add it to your path
I was using TestContainers and that was working ok (both locally and in the tekton pipelines) but then I switched to docker-compose to use the same file that we use on our day-to-day work and avoid having different versions in TestContainers vs docker-compose.
How to tell FluetDocker to communicate with that docker engine and not a "local" one? I think it's the http api vs native (correct me if I'm saying anything stupid 😄 )
The text was updated successfully, but these errors were encountered:
+1 interested, I have a dotnet core application that runs tests via dotnet test and I installed docker-cli and docker-compose to my test image with other deps as:
I'm trying to execute some integration tests using a docker-compose file that I'm passing it to the FluentDocker.
Locally (windows machine) it works ok because (I assume) I already have the docker running, so the FluentDocker knows how to connect to it.
In my case, I'm running a dind, so the tests are in one pod, and the docker is on another pod,
I'm getting this error:
Ductus.FluentDocker.Common.FluentDockerException : Failed to find docker client binary - please add it to your path
I was using TestContainers and that was working ok (both locally and in the tekton pipelines) but then I switched to docker-compose to use the same file that we use on our day-to-day work and avoid having different versions in TestContainers vs docker-compose.
How to tell FluetDocker to communicate with that docker engine and not a "local" one? I think it's the http api vs native (correct me if I'm saying anything stupid 😄 )
The text was updated successfully, but these errors were encountered: