Need `docker` installed on the helix images for Windows, to allow individual tests to create containers

[radical]

We have some EndToEnd tests in dotnet/aspire that use docker to start some containers, and then interact with them. The tests are sent as helix work items. And the individual tests then indirectly use docker to create containers.

build machine
    -> send-helix-workitems
        -> each workitem:
             -> `dotnet test ...`
                -> individual tests can use `docker.exe` to create multiple containers, and interact with them

This works on helix/linux with Ubuntu.2204.Amd64[.Open] queue. But not with the windows queues (tried Windows.10.Amd64.Client[.Open], Windows.10.Amd64.ServerRS5[.Open], and Windows.Amd64.Server2022[.Open]) as docker is not installed.

This is important for running integration/end-to-end tests for dotnet/aspire - which starts a bunch of containers for things like redis/mysql/etc.

This is a test run from helix/linux .

cc @dougbu @eerhardt @joperezr

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

[radical]

This is probably relevant - Run Docker Desktop for Windows in a VM or VDI environment.

[radical]

@dougbu Is there any other info that I can provide to help with this?

[dougbu]

I'm not sure that helps because I don't know if we are Docker Business customers. In any case, this issue has yet to be triaged or assigned and we're strapped at the moment.

[dougbu]

Adding to Ops - Service Maintenance /cc @garath and @ilyas1974.

Conversation about licensing issues and how we might do this work seems to have stalled. I'll nudge it…

[dougbu]

@radical you aren't part of that conversation. We'll report back once we have more information.

[ilyas1974]

While the two are related - mostly because we only have a single docker artifact that is used in both our build queues and our test queues, the images being referenced are different. You've made a link above between the two and I will make sure that when this is addressed, the other issue is also taken into account. I will let the Dev doing the work decide how he wants to address the github issue(s).

[riarenas]

@dougbu Can you point me to where the licensing conversations are happening? Is this something we can actually do, or we still don't know?