If a Pod with two containers shows only one container running while the other is in CrashLoopBackOff, what is the most probable cause?

medium📝 Troubleshoot Q6 of 15

Kubernetes - Pods

AThe Pod's node is out of resources, preventing the second container from starting

BThe failing container has an incorrect image or command causing it to crash

CKubernetes does not support multiple containers in a single Pod

DThe Pod's service account lacks permissions to run multiple containers

Step-by-Step Solution

Solution:

Step 1: Understand CrashLoopBackOff
This status indicates a container repeatedly crashes after starting.
Step 2: Identify common causes
Incorrect image, bad command, or missing dependencies often cause crashes.
Final Answer:
The failing container has an incorrect image or command causing it to crash -> Option B
Quick Check:
CrashLoopBackOff usually means container-level failure [OK]

Quick Trick: CrashLoopBackOff means container crashes repeatedly [OK]

Common Mistakes:

Master "Pods" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kubernetes Quizzes