- 最新
- 投票最多
- 评论最多
Hello Matteo,
The CrashLoopBackOff
error indicates that your pod had been started, but is failing to stay in Running
state.
Whenever the container running within the pod terminates, Kubernetes will restart the container. However, after a certain number of retries, if the container is still failing, Kubernetes will stop re-trying the container creation and mark the status as CrashLoopBackOff
.
You can run the kubectl describe pod <pod-name> -n <namespace>
command and look for the container Exit Code
to find out why the container is failing.
Before deploying the Image in EKS, try to run the docker container on your local workstation and find out if the container is able to stay in Running state.
I hope this helps. Please put a comment if you need further info.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
Thank you for your response. I have checked that my container remains in the "running" state and, for what concerns the Exit Code, I get 0 as a value. Can it be due to the fact that I have not created a CloudFormation stack?
The Exit Code 0 means that the process running inside the container has successfully exited. There is no issue with the container, however the process running within the container is unable to stay in Running state. Can you please provide me with the command that you used to run your docker container for testing?
I tried to upload the simulation application image from the AWS RoboMaker tutorial, so I have runned the command given in the Developer Guide