Skip to content

Explicitly start docker service in windows tests

Romuald Atchadé requested to merge start-docker-service-win-1809 into ajwalker/fix-build-on-custom-dir-test

What does this MR do?

Windows tests on win1809 machine started recently to fail with error similar to:

error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/info": open //./pipe/docker_engine: The system cannot find the file specified. (docker.go:754:0s)

After some investigation, we realize that, for whatever reason, explicitly starting the docker service on the windows machine was fixing the issue.

Why was this MR needed?

To allow the pipeline to pass.

What's the best way to test this MR?

No new failures in:

  • check windows 1809 unit test failures
  • check windows 1809 integration test failures

What are the relevant issue numbers?

Edited by Romuald Atchadé

Merge request reports