Interview Kubernetes, Docker, Helm & Podman

How do you view logs from a crashed (previous) container instance?

Kubernetes, Docker, Helm & Podman · Intermediate level

Answer

I view logs from the previous crashed container with kubectl logs POD -c CONTAINER --previous. That is important because the current container instance may not yet have produced logs or may be stuck restarting.

Technical explanation

--previous reads logs from the last terminated container instance, which is essential in CrashLoopBackOff.

If a Pod has multiple containers, always pass -c so you do not inspect the wrong container.

Troubleshooting starts from state and events: get, describe, logs, previous logs, events, and then node/runtime/network checks.

Separate scheduling failures, image pull failures, runtime failures, app failures, and traffic-routing failures so you do not fix the wrong layer.

Operational commands like drain and rollback must respect PDBs, probes, and workload disruption tolerance.

Hands-on example

1. In a non-production namespace, create this safe broken scenario: capture logs from the previous crashed container instance.

2. Follow a fixed triage order: kubectl get, describe, logs or logs --previous, events, rollout status, node status, and then runtime/network checks.

3. Fix only one variable at a time so the root cause is clear rather than accidentally masked.

4. Save the commands and final diagnosis as an interview-ready incident walkthrough.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More Kubernetes, Docker, Helm & Podman interview questions

← All Kubernetes, Docker, Helm & Podman questions