This happens when the container exits too quickly for logs to be captured, usually because it fails during startup.

If a container crashes immediately due to a bad command, missing file, or failed initialization, Kubernetes restarts it repeatedly. The useful error often appears only in the previous container run, not the current one. Pod events are also important here, because probes or exit codes often explain what’s happening long before logs do.

Many people focus only on live logs and miss the fact that Kubernetes keeps a short history of failed runs.

Takeaway: When logs look empty, pod events and previous container logs usually explain the crash.