This topic describes troubleshooting of pod issues for applications running on Serverless App Engine (SAE).
ImagePullBackOff
This error occurs when SAE cannot retrieve the container image within a pod.
Possible causes:
The image name is incorrect, such as a misspelling, or the image does not exist.
The image tag is incorrect, such as a misspelling, or the tag does not exist.
The image is in a private repository.
Solutions:
Verify and correct the image name and tag.
Upload the image to an Alibaba Cloud image repository. For more information, see the referenced document.
CrashLoopBackOff
This error indicates a container in the pod has failed to start.
Possible causes:
An application errors preventing container startup.
The container configurations are invalid.
The liveness probe has failed repeatedly.
Solutions:
Check real-time logs and events to determine the cause of the failure and adjust the relevant configurations accordingly.
A pod is not ready
A pod that is running but not ready indicates a failed readiness probe.
Possible causes:
A failed readiness probe means the pod is not connected to the service, and no traffic is being forwarded to the instance.
Solutions:
Access the webshell and execute the custom readiness probe command to verify the pod's functionality. If the pod is not functioning as expected, analyze the causes using real-time logs or events.