Fail to run command "docker run -d redis" for Docker Desktop 4.12.0 on "Windows Container"

[v-mengwe]

OS Version: Win10 21H2/Win11 21H2
Docker Desktop: 4.12.0(85335)
Regression: Preview Release

Repro Steps:

1. Make sure the docker for desktop mode is "Windows Container".
2. Open the D4W dashboard and switch to Docker Engine tab, update the value of "experimental" from "false" to "true".
3. Open command prompt or Windows Powershell as Administrator.
4. Start an arbitrary Windows container via command "docker run -d redis".
5. Check whether succeeds to run the command "docker run -d redis".

Expect:
Succeed to run the command "docker run -d redis".

Actual:
Fail to run command "docker run -d redis" with an error.

More info:

1. This issue doesn't reproduce on Docker for desktop 4.11.1 (84025).
2. This issue doesn't reproduce on Linux container.
3. This issue also reproduces for below commands on Windows container:

   docker run -d -P wordpress
   docker run -d -P ghost

[nicks]

Thank you for reporting! We're investigating...

[v-mengwe]

Verified on the latest build 4.12.0 (85629), this issue doesn't reproduce for now.

[nicks]

Thanks for following up!

[v-mengwe]

@nicks There is a confusion, this issue reproduces for now. Change the value of "experimental" from "false" to "true" and then restart Docker Desktop can't fix this issue. Verified the issue on 3 machines, all reproduced. We uninstalled and reinstalled D4W on the machine that was successful before and also reproduced this problem, so it may be caused by the old machine environment. Could you help investigate? Thanks!

[v-mengwe]

@nicks Do you have any updates?

[nicks]

oops sorry i misunderstood the original issue.

I believe this is currently expected behavior. I've confirmed it works the same way on 4.11.0.

If you have Docker Desktop in Windows Container mode, you won't be able to pull or run any new linux images.

Adding the ability to do this may be on the roadmap in the future, see this discussion: docker/roadmap#79

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked