This topic describes the limits on Elastic Container Instance.
Limits on elastic container instances
The following table describes the limits on elastic container instances.
Item | Limit | Remedy |
User accounts used to create an elastic container instance | When you create an elastic container instance in a region within the Chinese mainland, you must complete real-name verification for your account. | None. |
vCPUs that can be created within a region | The limit on each account varies based on the historical usage of the account. You can view your privileges and quotas on the Privileges page in the Elastic Container Instance console. | You can apply for a quota increase in the Quota Center console. |
vCPUs that can be allocated to an elastic container instance | 64 vCPU | None. |
Volumes that can be mounted to an elastic container instance | 20 | None. |
Containers that can be created in an elastic container instance | 20 | None. |
Network types | Only VPCs are supported. | None. |
Limits on API operations
The following table describes the maximum calls per minute on each API operation. If the quota for a specific API operation cannot meet your business requirements, you can submit a ticket to request a quota increase.
API operation | Maximum calls per minute | Increase the quota |
DescribeContainerGroups | 2000 | Submit a ticket. |
DescribeContainerGroupMetric | 2000 | Submit a ticket |
CreateContainerGroup | 1000 | Submit a ticket. |
DeleteContainerGroup | 1000 | Submit a ticket. |
DescribeContainerGroupPrice | 1000 | Submit a ticket. |
ExportContainerGroupTemplate | 1000 | Submit a ticket. |
ExecContainerCommand | 500 | Submit a ticket. |
DescribeContainerLog | 500 | Submit a ticket. |
RestartContainerGroup | 500 | Submit a ticket. |
UpdateContainerGroup | 500 | Submit a ticket. |
DescribeMultiContainerGroupMetric | 500 | Submit a ticket. |
CreateImageCache | 200 | Submit a ticket. |
Limits on Kubernetes
Elastic Container Instance uses virtual nodes to seamlessly connect to Kubernetes based on Virtual Kubelet provided by the Kubernetes community. Therefore, elastic container instances do not run on a centralized real node. They are scattered across the global Alibaba Cloud resource pool.
Elastic Container Instance does not support some Kubernetes features such as hostPaths and DaemonSets due to security limits of Alibaba Cloud public cloud and limits imposed by virtual nodes. The following table describes the unsupported features.
Unsupported feature | Description | Recommended alternative |
HostPath | Allows you to mount files from on-premises hosts to containers. | Use emptyDir volumes, disks, or File Storage NAS (NAS) file systems. |
HostNetwork | Allows you to map a host port to a container. | Create a Service of the LoadBalancer type. |
DaemonSet | Allows you to deploy a static pod on the host of a container. | Deploy multiple images in a pod by using sidecar containers. |
Service of the NodePort type | Allows you to map a host port to a container. | Create a Service of the LoadBalancer type. |
Limits on ulimit
Elastic Container Instance does not support ulimit. You can run the ulimit -a command in a container to query the default ulimit.
If you want to modify ulimit, submit a ticket.
Port usage
The following table describes ports used by Elastic Container Instance and related services. Do not use the following ports when you deploy services.
Port number | Description |
111, 10250, and 10255 | The ports used by the Elastic Container Instance interfaces such as exec, logs, and metrics |
998 | The port used by Cloud Paralleled File System (CPFS) |