Quotas and region availability for Azure Container Instances
All Azure services include certain default limits and quotas for resources and features. The following sections detail the default resource limits for several Azure Container Instances resources, as well as the availability of the service in Azure regions.
Service quotas and limits
|Container groups per subscription||1001|
|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 1000 lines|
|Container creates per hour||3001|
|Container creates per 5 minutes||1001|
|Container deletes per hour||3001|
|Container deletes per 5 minutes||1001|
1 Create an Azure support request to request a limit increase.
Azure Container Instances can schedule both Windows and Linux containers with the same API. However, the following features are currently available only in Linux container groups. Windows support is planned.
- Multiple containers per container group
- Volume mounting (Azure Files, emptyDir, GitRepo, secret)
- Virtual network (preview)
- GPU resources (preview)
Azure Container Instances is available in the following regions with the specified CPU and memory limits for each container group. Values are current at time of publication. For up-to-date information, use the List Capabilities API.
|Canada Central, Central US, East US 2, South Central US||Linux||4||16|
|East US, North Europe, West Europe, West US, West US 2||Linux||4||14|
|Australia East, Southeast Asia||Linux||2||7|
|Central India, East Asia, North Central US, South India||Linux||2||3.5|
|East US, West Europe, West US||Windows||4||14|
|Australia East, Canada Central, Central India, Central US, East Asia, East US 2, Japan East, North Central US, North Europe, South Central US, South India, Southeast Asia, West US 2||Windows||2||3.5|
Container instances 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 CPU and memory settings, or try your deployment at a later time.
Let the team know of additional regions required or increased CPU/Memory limits at aka.ms/aci/feedback.
For more information on troubleshooting container instance deployment, see Troubleshoot deployment issues with Azure Container Instances.
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 (select "Quota" for Issue type).
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.