You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From 8.0 preview 3, the .NET containers tagging scheme has changed - the multi-platform images no longer have windows platforms. The details are here.
Concretely, this means that we need to infer one of the 'concrete' windows container tags when the RID is win-x64. The windows tags that are available are:
8.0.0-preview.2-windowsservercore-ltsc2022
8.0.0-preview.2-windowsservercore-1809
8.0.0-preview.2-nanoserver-ltsc2022
8.0.0-preview.2-nanoserver-1809
We should bias to more minimal Windows images, so we should infer one of the nanoserver tags. We should add the following decision to our tag inference scheme:
if TARGET RID is win-x64
if CURRENT SDK RID is win-x64
use the windows OS version to choose what windows tag should be used:
if the windows version is >= 10.0.20348 then `nanoserver-ltsc2022`
else if the windows version is >= 10.0.17763 then `nanoserver-1809`
else fail
else
since we're on a non-windows OS we just assume the more recent nanoserver tag, `nanoserver-ltsc2022`
The text was updated successfully, but these errors were encountered:
We're not going to do this since we no longer infer windows base image names by default (per the change the dotnet-docker team made to the .NET images). If a user wants to use Windows containers they must specify a base image explicitly.
From 8.0 preview 3, the .NET containers tagging scheme has changed - the multi-platform images no longer have windows platforms. The details are here.
Concretely, this means that we need to infer one of the 'concrete' windows container tags when the RID is win-x64. The windows tags that are available are:
We should bias to more minimal Windows images, so we should infer one of the
nanoserver
tags. We should add the following decision to our tag inference scheme:The text was updated successfully, but these errors were encountered: