Merge pull request #277013 from alfpark/alpark/batch

Update Batch container docker issues

Author: prmerger-automator[bot]

articles/batch/batch-docker-container-workloads.md

@@ -2,7 +2,7 @@
 title: Container workloads on Azure Batch
 description: Learn how to run and scale apps from container images on Azure Batch. Create a pool of compute nodes that support running container tasks.
 ms.topic: how-to
-ms.date: 01/19/2024
+ms.date: 05/31/2024
 ms.devlang: csharp
 ms.custom: devx-track-csharp, linux-related-content
 ---
@@ -51,7 +51,7 @@ Keep in mind the following limitations:
 
 > [!IMPORTANT]
 > Docker, by default, will create a network bridge with a subnet specification of `172.17.0.0/16`. If you are specifying a
-> [virtual network](batch-virtual-network.md) for your pool, please ensure that there are no conflicting IP ranges.
+> [virtual network](batch-virtual-network.md) for your pool, ensure that there are no conflicting IP ranges.
 
 ## Supported VM images
 
@@ -77,6 +77,9 @@ without the need for a custom image.
 
 - Publisher: `microsoft-dsvm`
   - Offer: `ubuntu-hpc`
+- Publisher: `almalinux`
+  - Offer: `8-hpc-gen1`
+  - Offer: `8-hpc-gen2`
 
 #### Alternate image options
 
@@ -88,9 +91,9 @@ Currently there are other images published by `microsoft-azure-batch` that suppo
   - Offer: `ubuntu-server-container`
   - Offer: `ubuntu-server-container-rdma` (For use exclusively on VM SKUs with Infiniband)
 
-> [!IMPORTANT]
-> It is recommended to use the `microsoft-dsvm` `ubuntu-hpc` VM image instead of images published by
-> `microsoft-azure-batch`. This image may be used on any VM SKU.
+> [!WARNING]
+> It is recommended to use images other than those published by `microsoft-azure-batch` as these
+> images are deprecated due to imminent image end-of-life.
 
 #### Notes
   The docker data root of the above images lies in different places:
@@ -145,6 +148,13 @@ You can create a container-enabled pool with or without prefetched container ima
 
 The advantage of prefetching container images is that when tasks first start running, they don't have to wait for the container image to download. The container configuration pulls container images to the VMs when the pool is created. Tasks that run on the pool can then reference the list of container images and container run options.
 
+> [!NOTE]
+> Docker Hub limits the number of image pulls. Ensure that your workload doesn't
+> [exceed published rate limits](https://docs.docker.com/docker-hub/download-rate-limit/) for Docker
+> Hub-based images. It's recommended to use
+> [Azure Container Registry](../container-registry/container-registry-intro.md) directly or leverage
+> [Artifact cache in ACR](../container-registry/container-registry-artifact-cache.md).
+
 ### Pool without prefetched container images
 
 To configure a container-enabled pool without prefetched container images, define `ContainerConfiguration` and `VirtualMachineConfiguration` objects as shown in the following examples. These examples use the Ubuntu Server for Azure Batch container pools image from the Marketplace.

articles/batch/best-practices.md

@@ -1,7 +1,7 @@
 ---
 title: Best practices
 description: Learn best practices and useful tips for developing your Azure Batch solutions.
-ms.date: 04/02/2024
+ms.date: 05/31/2024
 ms.topic: conceptual
 ---
 
@@ -120,6 +120,19 @@ When you create an Azure Batch pool using the Virtual Machine Configuration, you
 
 Pools can be created using third-party images published to Azure Marketplace. With user subscription mode Batch accounts, you may see the error "Allocation failed due to marketplace purchase eligibility check" when creating a pool with certain third-party images. To resolve this error, accept the terms set by the publisher of the image. You can do so by using [Azure PowerShell](/powershell/module/azurerm.marketplaceordering/set-azurermmarketplaceterms) or [Azure CLI](/cli/azure/vm/image/terms).
 
+### Container pools
+
+When specifying a Batch pool with a [virtual network](batch-virtual-network.md), there can be interaction
+side effects between the specified virtual network and the default Docker bridge. Docker, by default, will
+create a network bridge with a subnet specification of `172.17.0.0/16`. Ensure that there are no conflicting
+IP ranges between the Docker network bridge and your virtual network.
+
+Docker Hub limits the number of image pulls. Ensure that your workload doesn't
+[exceed published rate limits](https://docs.docker.com/docker-hub/download-rate-limit/) for Docker
+Hub-based images. It's recommended to use
+[Azure Container Registry](../container-registry/container-registry-intro.md) directly or leverage
+[Artifact cache in ACR](../container-registry/container-registry-artifact-cache.md).
+
 ### Azure region dependency
 
 You shouldn't rely on a single Azure region if you have a time-sensitive or production workload. While rare, there are issues that can affect an entire region. For example, if your processing needs to start at a specific time, consider scaling up the pool in your primary region *well before your start time*. If that pool scale fails, you can fall back to scaling up a pool in a backup region (or regions).