Summary

DRIVERS-2570 introduced the functionality of detecting whether we are running in a container or not. The detection logic for docker was to check for the presence of a file namely ".dockerenv". However, that file isn't present in windows containers. This means the detection logic used by the drivers who implemented DRIVERS-2570 will not work for detecting docker if we are in a windows container.

We can detect docker in a windows container by checking if a particular windows service is running namely the "CExecSvc" service. This service only runs when we are in a container and can serve as a reliable way to detect docker for windows containers. According to the Windows Internals book part 1, this service is responsible for implementing the container execution service which establishes communication through a named pipe with the Docker and Vmcompute services on the host. 

Motivation

Who is the affected end user?

Probably the sales team who will be able to get more info about container usage for windows users.

How does this affect the end user?

No direct impact to the end users.

How likely is it that this problem or use case will occur?

Already occurring.

If the problem does occur, what are the consequences and how severe are they?

We will not get info about docker usage for customers running in windows containers.

Is this issue urgent?

Could be blocking valuable product insights.

Is this ticket required by a downstream team?

Growth Sales team?

Is this ticket only for tests?

Analytics, product value tracking, sales efforts