Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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.
Values presented are the maximum resources available per deployment of a container group. Values are current at time of publication.
Note
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.
Default Quota Limits
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.
Use the List Usage API to review current quota usage in a region for a subscription.
Certain default limits and quotas can be increased. To request an increase of one or more resources that support such an increase, submit an Azure support request (select "Quota" for Issue type).
Important
Not all limit increase requests are guaranteed to be approved. Deployments with GPU resources aren't supported in an Azure virtual network deployment and are only available on Linux container groups. Using GPU resources (preview) isn't fully supported yet and any support is provided on a best-effort basis.
Unchangeable (Hard) Limits
The following limits are default limits that can’t be increased through a quota request. Any quota increase requests for these limits won't be approved.
| Resource | Actual Limit |
|---|---|
| Number of containers per container group | 60 |
| Number of volumes per container group | 20 |
| Ports per IP | 5 |
| Container instance log size - running instance | 4 MB |
| Container instance log size - stopped instance | 16 KB or 1,000 lines |
Changeable Limits (Eligible for Quota Increases)
| Resource | Actual Limit |
|---|---|
| Standard sku container groups per region per subscription | 100 |
| Standard sku cores (CPUs) per region per subscription | 100 |
| Standard sku cores (CPUs) for V100 GPU per region per subscription | 0 |
| Container group creates per hour | 3001 |
| Container group creates per 5 minutes | 1001 |
| Container group deletes per hour | 3001 |
| Container group deletes per 5 minutes | 1001 |
Note
1: Indicates that the feature maximum is configurable and may be increased through a support request. For more information on how to request a quota increase, see the How to request a quota increase section of Increase VM-family vCPU quotes.
You can also create a support ticket if you'd like to discuss your specific needs with the support team.
Standard Container Resources
By default, the following resources are available general purpose (standard core SKU) containers in general deployments and Azure virtual network deployments) for Linux & Windows containers. These maximums are hard limits and can't be increased.
Generally Available Limits:
| Max CPU | Max Memory (GB) | Virtual network Max CPU | Virtual network Max Memory (GB) | Storage (GB) |
|---|---|---|---|---|
| 4 | 16 | 4 | 16 | 50 |
For a general list of available regions for Azure Container Instances, see available regions.
Preview Limits:
Note
Big Container SKUs are in preview, and you may experience errors in some regions that you deploy. Preview features aren't ideal for critical workloads. If you're experiencing errors when deploying containers with greater than 4 vCPU and 16 GB in a certain region, please submit an Azure support request (select "Quota" for Support type).
| Max CPU | Max Memory (GB) | Virtual network Max CPU | Virtual network Max Memory (GB) | Storage (GB) |
|---|---|---|---|---|
| 32 | 256 | 32 | 256 | 50 |
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.
Confidential Container Resources
The following maximum resources are available to a container group deployed using Confidential Containers. These maximums are hard limits and can't be increased.
Generally Available Limits:
| Max CPU | Max Memory (GB) | Virtual network Max CPU | Virtual network Max Memory (GB) | Storage (GB) |
|---|---|---|---|---|
| 4 | 16 | 4 | 256 | 50 |
Preview Limits:
Note
Big Container SKUs are in preview, and you may experience errors in some regions that you deploy. Preview features aren't ideal for critical workloads. If you're experiencing errors when deploying containers with greater than 4 vCPU and 16 GB in a certain region, please submit an Azure support request (select "Quota" for Support type).
| Max CPU | Max Memory (GB) | Virtual network Max CPU | Virtual network Max Memory (GB) | Storage (GB) |
|---|---|---|---|---|
| 32 | 192 | 32 | 192 | 50 |
Spot Container Resources (Preview)
The following maximum resources are available to a container group deployed using Spot Containers (preview). These maximums are hard limits and can't be increased.
Note
Spot Containers are only available in the following regions at this time: East US 2, West Europe, and West US.
| Max CPU | Max Memory (GB) | Virtual network Max CPU | Virtual network Max Memory (GB) | Storage (GB) |
|---|---|---|---|---|
| 4 | 16 | N/A | N/A | 50 |
GPU Container Resources (Preview)
Important
K80 and P100 GPU SKUs were retired on August 31st, 2023. This is due to the retirement of the underlying VMs used: NC Series and NCv2 Series Although V100 SKUs will be available, it's recommended to use Azure Kubernetes Service instead. GPU resources aren't fully supported and shouldn't be used for production workloads. Use the following resources to migrate to AKS today: How to Migrate to AKS.
Note
Not all limit increase requests are guaranteed to be approved. Deployments with GPU resources aren't supported in an Azure virtual network deployment and are only available on Linux container groups. Using GPU resources (preview) isn't fully supported yet and any support is provided on a best-effort basis.
The following maximum resources are available to a container group deployed with GPU resources (preview). These maximums are hard limits and can't be increased.
| GPU SKUs | GPU count | Max CPU | Max Memory (GB) | Storage (GB) |
|---|---|---|---|---|
| V100 | 1 | 6 | 112 | 50 |
| V100 | 2 | 12 | 224 | 50 |
| V100 | 4 | 24 | 448 | 50 |
Next steps
Certain default limits and quotas can be increased. To request an increase of one or more resources that support such an increase, submit an Azure support request (select "Quota" for Issue type).
Let the team know if you'd like to see other regions or increased resource availability at aka.ms/aci/feedback.
For information on troubleshooting container instance deployment, see Troubleshoot deployment issues with Azure Container Instances.