Kubernetes Container Failing and stuck in CrashLoopBackOff status with no events/logs in pods

2/4/2020

My container in Kubernetes is failing and stuck in CrashLoopBackOff state with no logs/events to track the error.

enter image description here

Above screenshot is taken through Azure Kubernets Extensions on VS Code There is no visible logs for me to further investigate the issue.

In Container description, it says it's terminated due to exit code 134. enter image description here

What does this error code mean? and where can I find the logs for container termination?

-- Evan Park
azure-kubernetes
containers
docker
kubernetes

0 Answers