This topic describes different statuses in the lifecycle of an Elastic Container Instance (ECI) or a container. You can design your business logic based on these statuses. ECI is seamlessly integrated with Kubernetes. You can directly use ECIs as pods in Kubernetes clusters.

ECI statuses

Scheduling: The ECI is being created.

Pending: One or more containers in the ECI are being started and none is running.

Running: All containers in the ECI are created, and at least one container is running or restarting.

Restarting: The ECI is restarting.

Updating: The ECI is being updated.

Succeeded: All containers in the ECI are terminated in success and will not be restarted.

Failed: All containers in the ECI are terminated, and at least one containers is terminated in failure. That is, the container exits with a non-zero exit code or is terminated by the system.

Expired: The ECI is a preemptible instance and has been terminated when its resources expire and are reclaimed.

ScheduleFailed: The ECI fails to be created. The ECI will be automatically deleted after 24 hours. No fee is charged for an ECI in this state.

StartingFailed: The ECI fails to be started. An ECI automatically enters the StartingFailed state after it stays in the Pending state for 4 hours, and computing resources are released. No fee is charged for an ECI in this state.

WatingForDel: The ECI is waiting to be deleted. An ECI automatically enters the WatingForDel state after it stays in the ScheduleFailed state for 1 hour. No fee is charged for an ECI in this state.

Warning The restart policy of an ECI only applies to the containers in the ECI. An ECI does not automatically restart.

Container statuses

Waiting: The container is waiting to be created and is not running. Generally, application containers remain in the Waiting state when an init container is running until the init container exits.

Running: The container is created and running.

Terminated: The container is terminated in success or in failure.