Summary of Impact

Microsoft is removing Windows Server Container images on April 30, 2023 from the Marketplace.

• Initial announcement on September 27, 2021
• Reminder announcement on September 8, 2022
• Update announcement on October 6, 2022

As per the announcement, the following images will be removed from the Marketplace:

• 2016-Datacenter-with-Containers
• 2016-datacenter-with-containers-g2
• 2016-Datacenter-with-Containers-GS
• 2019-Datacenter-Core-with-Containers
• 2019-datacenter-core-with-containers-g2
• 2019-Datacenter-Core-with-Containers-smalldisk
• 2019-datacenter-core-with-containers-smalldisk-g2
• 2019-Datacenter-with-Containers
• 2019-datacenter-with-containers-g2
• 2019-Datacenter-with-Containers-GS
• 2019-Datacenter-with-Containers-smalldisk
• 2019-datacenter-with-containers-smalldisk-g2
• datacenter-core-20h2-with-containers-smalldisk
• datacenter-core-20h2-with-containers-smalldisk-gs
• datacenter-core-20h2-with-containers-smalldisk-g2

Any of the images listed above that are permissible to be deployed as a Batch pool will no longer work properly after the removal date. Batch pools will no longer be able to be created with these images and will no longer be able to be scaled out. Additionally, continuity for existing nodes in pools with these images are not guaranteed and may be broken (i.e., scaled in, unusable, etc.).

Recommendation and Guidance

Option 1: Custom Image

Note that Batch's DockerCompatible API does not support containerd with a CLI with docker compatibility. containerd is not currently compatible with Batch containers, even with a compatible CLI. Please install a Docker Engine compatible runtime to satisfy the Batch DockerCompatible runtime requirement: Docker CE, moby, or Mirantis Container Runtime.

Customers are recommended to follow the linked announcements above and create a Batch-compatible custom image hosted in a Azure Compute Image Gallery that is compatible with Azure Batch container pools and tasks. Workloads should be migrated from existing Batch pools that use the images that will be retired (as listed above) to Batch pools based on the custom image before the image removal date.

Note that you cannot use the option to install the Docker-compatible runtime during VM start with Custom Script Extension as that extension is reserved for Batch pools. We recommend that you preload the Docker-compatible runtime (and any necessary support licenses, if applicable) with a custom image using Azure Image Builder, Packer, or manually. Additionally, you cannot install the Docker-compatible runtime as part of your start task and utilize native Batch container functionality. The Docker-compatible runtime must be present as part of the custom image.

Option 2: Mirantis Marketplace VM Image

Customers that have user subscription Batch accounts can create a new pool based on Mirantis published images that have the Mirantis Container Runtime pre-installed. Please note the applicable pricing on these images. These images are:

• Windows Server 2016 Datacenter with MCR
• Windows Server 2019 Datacenter with MCR
• Windows Server 2022 Datacenter with MCR

We highly recommend that you test your workloads thoroughly before migrating your production workloads to pools backed by these Mirantis images. Note that Azure Batch has marked these images as unverified meaning that although Batch allows deployment to these images, the service has not fully validated functionality against these images.

Runtime Support

Neither Microsoft or Batch will provide support for issues related to Docker CE or Moby runtimes. Customers electing to use the Mirantis Container Runtime should reach out to Mirantis for support.