1909 (SAC): docker pull /windows/servercore:1909.ltsc2019 (LTSC): docker pull /windows/servercore:ltsc2019.New Windows Server Base OS container images go live shortly after 10:00am PST on the second Tuesday of each month in the Microsoft Container Registry (MCR), and the featured tags target the most recent B release. To learn more about the Windows update servicing cadence, see our Windows update servicing cadence blog post. The server hosting these containers, called the container host or just the "host", can be serviced during additional update events other than "B" releases. For example, we call our February update "2B" and our March update "3B." This monthly update event is the only regular release that include new security fixes.
Updated container images are published the second Tuesday of each month, which we sometimes refer to as our "B" release, with a prefix number based on the release month. We update Windows Server Base OS container images in alignment with the Windows servicing cadence. How to get Windows Server container updates NET or IIS, will be rebuilt based on the updated Base OS container images and published monthly. Therefore, every month we rebuild the Windows Server Base OS container images with the updates and publish the updated container images. You can't get updates within a container like you do with Windows Server. Windows Server containers don't have a servicing stack like Windows Server. With these updates, you can automate building updated container images or manually update them by pulling the latest version. Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016Īs part of servicing Windows Server each month, we publish updated Windows Server Base OS container images on a regular basis.
0 kommentar(er)
