-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
I just wanted to get some clarification for planning on the life cycle of using .net core on Docker on a Windows Server.
Over the past year, all of the official .net core 2016 images have stopped being supported mostly because the underlying supported nanoserver versions that they use as the base reached end of life.
Although the server version may be LTSC, the official .net core images are based on nanoserver which uses the Semi Annual Channel and is only supported for 1.5 to sometimes 2 years. Potentially meaning that the an official .net core docker image for each major server version (2016/2019/etc) would only be supported up to 1 year after the release of the next major server version.
For example the latest nanoserver will reach EOL in 5/2021. If a new version of Windows Server comes out this year, is the plan that official .net core images will only be kept being supported on 2019 until 2022 assuming one more version of nanoserver that works on 2019 is released as well this year.
Then for planning purposes, for an application running in docker with .net core to keep using official images, the application will have to be migrated to a new Windows Server version potentially within a year of its release in order to not have to roll your own image using the larger servercore images.
Additional References:
#1041 - Nano Server 2016 and 1709 no longer Supported by .NET Core
#1469 - Windows Server, version 1803 no longer supported by .NET Core
Base Image Lifecycle
Windows Server End of Life
Servicing Channels