This message was deleted.

In order to understand what is causing this error, we need to understand what your test suite defines as a "Docker environment". This could mean a bunch of things, for example: • a

docker

command somewhere on your

PATH

•

/var/run/docker.sock

, which the tests might use to connect to the docker daemon It could be something else too. My advice is to understand how your test suite talks to docker - once that is done I can help you with the Rancher Desktop side 🙂

thanks, @jolly-forest-99711. let me check the tests and see how the "docker" is invoked.