- Documentation
Volcengine Kubernetes Engine
Volcengine Kubernetes Engine
FAQs
Workload FAQs
Why is the pod instance always in the "ContainerCreating" state after the workload is created?
Workload FAQs
Why is the pod instance always in the "ContainerCreating" state after the workload is created?
Why is the pod instance always in the "ContainerCreating" state after the workload is created?
Issue description
- A workload (Deployment, StatefulSet, DaemonSet, Job, or CronJob) was created.
- On the workload details page, the pod instance remains in the ContainerCreating state.
Solution
After you select the container image when creating a workload, if you do not specify an image tag, the system pulls the image with the latest tag by default. If the selected image does not have a version with the latest tag, the issue described above will occur.
Update the workload by following the steps below:
- In the upper-right corner of the workload details page, click Update.
- The following figure uses the Deployment details page as an example.
- In the Container configuration step of the workload update procedure, select a specific image tag and complete the update according to the configuration wizard.
- On the List of instances tab of the workload details page, view the pod instance status. If the status is Running, the workload has been successfully created and is running normally.
Last updated: 2026.07.23 14:31:46