Today we announced the General Availability (GA) of Windows Server 2022. It is such an exciting milestone for the Windows Server community and the broader ecosystem. As someone who shipped the last few Windows Server releases and have been working with teams across Microsoft to bring Windows Server 2022 to GA, I am thrilled to share this with our Windows Server container community!
As outlined in this What’s new for Windows Containers on Windows Server 2022 blog, Windows Server 2022 brings innovations and improvements in Windows Server container platform, application compatibility and containerization tooling. In addition, a new Server container image that supports better application compatibility for Server applications was introduced with this release as shared in this Announcing a New Windows Server Container Image Preview blog.
The most exciting part with this release is we are aiming to work with the Kubernetes community to enable Windows Server 2022 support there, bring it to Azure Kubernetes Service (AKS) and Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) and support the whole ecosystem to adopt as well. We are excited to share the following PRs are already submitted in the Kubernetes community:
In addition, these test jobs on networking are being added:
There will be more coming as we continue to work with the Kubernetes community on this journey. You are welcome to contribute as well.
With the upcoming deprecation of dockershim in Kubernetes, we intended to support containerd as the only container runtime for Windows Server 2022 on Microsoft’s first party Kubernetes services aka AKS and AKS-HCI. We started the containerd work back in Windows Server 2019 and have been supporting containerd internally for various Azure services. This containerd-only focus starting with Windows Server 2022 aligns with where the ecosystem is going and will give our customers a more robust and performant experience. Containerd support for Windows Server 2019 on AKS is already in preview per this update Azure Kubernetes Service (AKS) support for containerd runtime is in preview.
Windows base OS images by Microsoft is the landing page of the product family of all Windows Server base OS container images. As usual the actual images are available on Microsoft Container Registry (MCR). This release comes with these 3 container images types:
For those of you using the Windows base OS image and wanting to run the image on a Windows Server 2022 host in Process Isolation, you will need to switch to use that new Server base OS image instead. Otherwise, you can run the Windows base OS image with Hyper-V isolation on a Windows Server 2022 host. You can always check out more details on container host and container image version compatibility at the Windows container version compatibility documentation page.
If you are interested in container images from other teams from Microsoft, the following are also available for Windows Server 2022:
There will be 3 types of tags for this release:
For example, this is how you pull Windows Server 2022 container images:
As we move forward with monthly patches, you can still use the featured tag and get the latest images; or you can specify the specific KB number or the build number for a specific release. You can use the Windows Server container update history for reference.
We are actively working with the Kubernetes community as well as our own AKS and AKS-HCI teams to bring up Windows Server 2022 support. To keep up to date on when Windows Server 2022 will be available on AKS and AKS-HCI, please follow these GitHub threads:
We would love for our customers and community to try out and let us know your feedback. Please feel free to post in our Windows Container GitHub community.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.