Running dockers as `--isolation=process` on Win10 21H1

[roozbehid]

I cannot find any version of windows image to be able to run on Windows 10.0.19043.x (21H1) with "--isolation=process"

This page says you should be able to run 20H2 (?) on 21H1.
https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2022%2Cwindows-10-21H1#windows-client-host-os-compatibility

Am I missing something here?

[roozbehid]

Also to be more confused (at least on my side) what would be the case for Windows 10 21H2, is it similar to Windows 11 21H2 and can run Windows Server 2022?

[roozbehid]

Talking to myself :D it seems answer is no as build number on Windows 10 stays same so Windows 10 21H2 like Windows 10 21H! wont support inprocess.
#117

This issue has been open for 30 days with no updates.
, please provide an update or close this issue.

[QuAzI]

Nothing works with W10 21H2 which is marked as LTSC

[slonopotamus]

This page says you should be able to run 20H2 (?) on 21H1

That page lies.

[vrapolinario]

Microsoft did not release a 21H1 container image as you can see here: https://hub.docker.com/_/microsoft-windows-servercore. (This one is Server Core, but other images follow this) The latest one is ltsc2022 which is ahead of Win10. You can run LTSC2022 on Win11 with process isolation. We clarified some of this on this blog post: https://techcommunity.microsoft.com/t5/containers/windows-server-2022-and-beyond-for-containers/ba-p/2712487

I assigned the folks that are working on this to this thread so they can provide the latest on this.

[vrapolinario]

And as for the docs page, I will follow up with the Docs team to fix the error on the page.

[QuAzI]

@vrapolinario
Will we have a chance to have containers for W10 21H2? We need it because downgrade to 20H2 impossible