Error on IntegrationTestsFixture and detect host configuration

[exile69000]

I'm running tests from CI/CD on AzureDevOps.

I have two errors : "The following constructor parameters did not have matching fixture data: IntegrationTestsFixture fixture" and "Auto discovery did not detect a Docker host configuration".

I don't know what happen, on my local computer test is ok.

thanks for your help :)

[HofmeisterAn]

Docker is either not running or misconfigured.

Are you running on a private CI agent? Does the CI agent contain a Docker runtime? This error message usually indicates that there is no Docker (container) runtime available. Please make sure Docker is installed.

[exile69000]

Yes I'm running on private CI agent, I created Linux Agent, on Debian server I installed Docker and Docker Desktop:

My Nugets TestContainers are up to date.
This is my pipeline :

Is there a command to check if Docker is correctly installed and CI Agent use Docker runtime ?

[HofmeisterAn]

Yes I'm running on private CI agent, I created Linux Agent, on Debian server I installed Docker and Docker Desktop:

Ok, that's good. It looks like Testcontainers does not found the daemon. Can you share the output of

docker context ls

Is there a command to check if Docker is correctly installed and CI Agent use Docker runtime ?

docker run hello-world should be fine.

[exile69000]

Output of docker context ls :

Maybe I have to specify the DOCKER_HOST in .testcontainers.properties ?

[exile69000]

I think I have not permission :

[HofmeisterAn]

Yep, that looks like the issue. I do not know your environment, so I am afraid I cannot provide much assistance here. If a Docker group exists, you might want to consider adding the agent user to that group.

[exile69000]

I added user in Docker group, restart docker engine but same issue....
If I created .testcontainers.properties in my folder user like this it's good :
docker.host=unix:///var/run/docker.sock

[exile69000]

So I found solution ! I add my user in sudo group and it's working :)

[HofmeisterAn]

Please be careful; this will grant essentially administrative privileges to your build user, not always something you want.

[exile69000]

Yes you’re right ! I need to see with my network team to resolve this issue, in any case it’s working