Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Server, version 1803 no longer supported by .NET Framework #141

Open
MichaelSimons opened this issue Nov 15, 2019 · 0 comments
Open

Windows Server, version 1803 no longer supported by .NET Framework #141

MichaelSimons opened this issue Nov 15, 2019 · 0 comments

Comments

@MichaelSimons
Copy link
Collaborator

@MichaelSimons MichaelSimons commented Nov 15, 2019

Windows Server, version 1803 no longer supported by .NET Framework

Windows Server, version 1803 is no longer supported. As a result, this version of Windows is no longer supported by the .NET Team and we will no longer produce .NET Framework container images for this Windows version.

Support statements:

Discussion

Please share your thoughts on this change and see what others are saying at:

Details

Docker tags that contain windowsservercore-1803 are no longer being produced. We will not delete existing images or those tags. However, they contain unsupported builds of Windows Server and .NET Framework.

Pulling manifest tags

These changes also affect manifest tags (AKA “multi-arch tags“), such as 4.8. These are tags that are supported on multiple operating systems and versions, and do not contain the operating system in them. As a result of no longer producing new images for Windows Server, version 1803, manifest tags no longer include entries for Windows 10, version 1803, and Windows Server, version 1803. That means that .NET Core manifest tags are no longer usable on those Windows versions.

If you pull a manifest tag on one of the Windows versions described, you may get one of the following error messages:

  • a Windows version 10.0.18362-based image is incompatible with a 10.0.17134 host
  • no matching manifest for windows/amd64 in the manifest list entries
  • no matching manifest for unknown in the manifest list entries

If you need to still use Windows Server, version 1803 images (even though they are no longer supported), you will need to use tags that include the Windows Server version (these are non-manifest tags), for example mcr.microsoft.com/dotnet/framework/runtime:4.8-windowsservercore-1803 or mcr.microsoft.com/dotnet/framework/sdk:4.8-windowsservercore-1803.

@dotnet dotnet locked and limited conversation to collaborators Nov 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant
You can’t perform that action at this time.