Skip to content

Commit 8201e81

Browse files
Stacyrch140Stacyrch140
authored
Merge pull request #225011 from tysonfms/main
Updating VNET, region availability, and other docs
2 parents ed0b0f4 + c1b5f8a commit 8201e81

File tree

4 files changed

+129
-8
lines changed

4 files changed

+129
-8
lines changed

‎articles/container-instances/TOC.yml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
items:
55
- name: About Azure Container Instances
66
href: container-instances-overview.md
7+
- name: Resources and Quota Limits
8+
href: container-instances-resource-and-quota-limits.md
79
- name: Quickstarts
810
expanded: true
911
items:
@@ -53,10 +55,8 @@
5355
items:
5456
- name: Container groups
5557
href: container-instances-container-groups.md
56-
- name: Quotas and limits
57-
href: container-instances-quotas.md
58-
- name: Region availability
59-
href: container-instances-region-availability.md
58+
- name: Region and resource availability
59+
href: container-instances-resource-and-quota-limits.md
6060
- name: Relationship to orchestrators
6161
href: container-instances-orchestrator-relationship.md
6262
- name: Security
@@ -185,7 +185,7 @@
185185
- name: Build your skills with Microsoft Learn training
186186
href: /training/browse/?products=azure-container-instances
187187
- name: Region availability
188-
href: https://azure.microsoft.com/regions/services/
188+
href: https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/?products=container-instances
189189
- name: Pricing
190190
href: https://azure.microsoft.com/pricing/details/container-instances/
191191
- name: Roadmap

‎articles/container-instances/container-instances-resource-and-quota-limits.md

Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
---
2+
title: Resource availability & quota limits for ACI
3+
description: Availability and quota limits of compute and memory resources for the Azure Container Instances service in different Azure regions.
4+
ms.author: tomcassidy
5+
author: tomvcassidy
6+
ms.service: container-instances
7+
services: container-instances
8+
ms.topic: conceptual
9+
ms.date: 1/19/2023
10+
ms.custom: references_regions
11+
12+
---
13+
# Resource availability & quota limits for ACI
14+
15+
This article details the availability and quota limits of Azure Container Instances compute, memory, and storage resources in Azure regions and by target operating system. For a general list of available regions for Azure Container Instances, see [available regions](https://azure.microsoft.com/regions/services/).
16+
17+
Values presented are the maximum resources available per deployment of a [container group](container-instances-container-groups.md). Values are current at time of publication.
18+
19+
> [!NOTE]
20+
> Container groups created within these resource limits are subject to availability within the deployment region. When a region is under heavy load, you may experience a failure when deploying instances. To mitigate such a deployment failure, try deploying instances with lower resource settings, or try your deployment at a later time or in a different region with available resources.
21+
22+
## Default Quota Limits
23+
24+
All Azure services include certain default limits and quotas for resources and features. This section details the default quotas and limits for Azure Container Instances.
25+
26+
Use the [List Usage](/rest/api/container-instances/location/listusage) API to review current quota usage in a region for a subscription.
27+
28+
Certain default limits and quotas can be increased. To request an increase of one or more resources that support such an increase, please submit an [Azure support request][azure-support] (select "Quota" for **Issue type**).
29+
30+
> [!IMPORTANT]
31+
> Not all limit increase requests are guaranteed to be approved.
32+
> Deployments with GPU resources are not supported in an Azure virtual network deployment and are only available on Linux container groups.
33+
> Using GPU resources (preview) is not fully supported yet and any support is provided on a best-effort basis.
34+
35+
### Unchangeable (Hard) Limits
36+
37+
The following limits are default limits that can’t be increased through a quota request. Any quota increase requests for these limits will not be approved.
38+
39+
| Resource | Actual Limit |
40+
| --- | :--- |
41+
| Number of containers per container group | 60 |
42+
| Number of volumes per container group | 20 |
43+
| Ports per IP | 5 |
44+
| Container instance log size - running instance | 4 MB |
45+
| Container instance log size - stopped instance | 16 KB or 1,000 lines |
46+
47+
48+
### Changeable Limits (Eligible for Quota Increases)
49+
50+
| Resource | Actual Limit |
51+
| --- | :--- |
52+
| Standard sku container groups per region per subscription | 100 |
53+
| Standard sku cores (CPUs) per region per subscription | 100 |
54+
| Standard sku cores (CPUs) for K80 GPU per region per subscription | 0 |
55+
| Standard sku cores (CPUs) for V100 GPU per region per subscription | 0 |
56+
| Container group creates per hour |300<sup>1</sup> |
57+
| Container group creates per 5 minutes | 100<sup>1</sup> |
58+
| Container group deletes per hour | 300<sup>1</sup> |
59+
| Container group deletes per 5 minutes | 100<sup>1</sup> |
60+
61+
## Standard Core Resources
62+
63+
### Linux Container Groups
64+
65+
By default, the following resources are available general purpose (standard core SKU) containers in general deployments and [Azure virtual network](container-instances-vnet.md) deployments) for Linux & Windows containers.
66+
67+
| Max CPU | Max Memory (GB) | VNET Max CPU | VNET Max Memory (GB) | Storage (GB) |
68+
| :---: | :---: | :----: | :-----: | :-------: |
69+
| 4 | 16 | 4 | 16 | 50 |
70+
71+
For a general list of available regions for Azure Container Instances, see [available regions](https://azure.microsoft.com/regions/services/).
72+
73+
### Windows Containers
74+
75+
The following regions and maximum resources are available to container groups with [supported and preview](./container-instances-faq.yml) Windows Server containers.
76+
77+
#### Windows Server 2019 LTSC
78+
79+
> [!NOTE]
80+
> 1B and 2B hosts have been deprecated for Windows Server 2019 LSTC. See [Host and container version compatibility](/virtualization/windowscontainers/deploy-containers/update-containers#host-and-container-version-compatibility) for more information on 1B, 2B, and 3B hosts.
81+
82+
The following resources are available in all Azure Regions supported by Azure Container Instances. For a general list of available regions for Azure Container Instances, see [available regions](https://azure.microsoft.com/regions/services/).
83+
84+
| 3B Max CPU | 3B Max Memory (GB) | Storage (GB) | Availability Zone support |
85+
| :----: | :-----: | :-------: |
86+
| 4 | 16 | 20 | Y |
87+
88+
## GPU Resources (Preview)
89+
90+
> [!IMPORTANT]
91+
> Not all limit increase requests are guaranteed to be approved.
92+
> Deployments with GPU resources are not supported in an Azure virtual network deployment and are only available on Linux container groups.
93+
> Using GPU resources (preview) is not fully supported yet and any support is provided on a best-effort basis.
94+
95+
The following maximum resources are available to a container group deployed with [GPU resources](container-instances-gpu.md) (preview).
96+
97+
| GPU SKUs | GPU count | Max CPU | Max Memory (GB) | Storage (GB) |
98+
| --- | --- | --- | --- | --- |
99+
| K80 | 1 | 6 | 56 | 50 |
100+
| K80 | 2 | 12 | 112 | 50 |
101+
| K80 | 4 | 24 | 224 | 50 |
102+
| P100, V100 | 1 | 6 | 112 | 50 |
103+
| P100, V100 | 2 | 12 | 224 | 50 |
104+
| P100, V100 | 4 | 24 | 448 | 50 |
105+
106+
## Next steps
107+
108+
Certain default limits and quotas can be increased. To request an increase of one or more resources that support such an increase, please submit an [Azure support request][azure-support] (select "Quota" for **Issue type**).
109+
110+
Let the team know if you'd like to see additional regions or increased resource availability at [aka.ms/aci/feedback](https://aka.ms/aci/feedback).
111+
112+
For information on troubleshooting container instance deployment, see [Troubleshoot deployment issues with Azure Container Instances](container-instances-troubleshooting.md)
113+
114+
<!-- LINKS - External -->
115+
116+
[az-region-support]: ../availability-zones/az-overview.md#regions
117+
118+
[azure-support]: https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest
119+
120+
121+
122+

‎articles/container-instances/container-instances-virtual-network-concepts.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.date: 06/17/2022
1616
This article provides background about virtual network scenarios, limitations, and resources. For deployment examples using the Azure CLI, see [Deploy container instances into an Azure virtual network](container-instances-vnet.md).
1717

1818
> [!IMPORTANT]
19-
> Container group deployment to a virtual network is generally available for Linux containers, in most regions where Azure Container Instances is available. For details, see [Regions and resource availability](container-instances-region-availability.md).
19+
> Container group deployment to a virtual network is generally available for Linux and Windows containers, in most regions where Azure Container Instances is available. For details, see [Regions and resource availability](container-instances-region-availability.md).
2020
2121
## Scenarios
2222

@@ -38,7 +38,6 @@ Container groups deployed into an Azure virtual network enable scenarios like:
3838

3939
## Other limitations
4040

41-
* Currently, only Linux containers are supported in a container group deployed to a virtual network.
4241
* To deploy container groups to a subnet, the subnet can't contain other resource types. Remove all existing resources from an existing subnet prior to deploying container groups to it, or create a new subnet.
4342
* To deploy container groups to a subnet, the subnet and the container group must be on the same Azure subscription.
4443
* You can't enable a [liveness probe](container-instances-liveness-probe.md) or [readiness probe](container-instances-readiness-probe.md) in a container group deployed to a virtual network.

‎articles/container-instances/container-instances-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This article shows how to use the [az container create][az-container-create] com
1919
For networking scenarios and limitations, see [Virtual network scenarios and resources for Azure Container Instances](container-instances-virtual-network-concepts.md).
2020

2121
> [!IMPORTANT]
22-
> Container group deployment to a virtual network is generally available for Linux containers, in most regions where Azure Container Instances is available. For details, see [Regions and resource availability][container-regions].
22+
> Container group deployment to a virtual network is generally available for Linux and Windows containers, in most regions where Azure Container Instances is available. For details, see [Regions and resource availability][container-regions].
2323
2424
[!INCLUDE [network profile callout](./includes/network-profile/network-profile-callout.md)]
2525

0 commit comments

Comments
 (0)