[Solved] Why does this Pod fail to start?initContainers: - name: init image: busybox command: ['sh', '-c', 'exit 1'] | Kubernetes

Kubernetes - Pods

Why does this Pod fail to start?

initContainers:
- name: init
  image: busybox
  command: ['sh', '-c', 'exit 1']

AThe Pod spec is missing main containers

BThe image 'busybox' is not allowed for init containers

CThe command syntax is invalid

DThe init container exits with failure, blocking Pod start

Step-by-Step Solution

Solution:

Step 1: Analyze init container command
The command 'exit 1' causes the init container to fail immediately.
Step 2: Understand Pod startup rules
Pod startup is blocked until init containers succeed; failure prevents Pod from running.
Final Answer:
The init container exits with failure, blocking Pod start -> Option D
Quick Check:
Init container failure blocks Pod start [OK]

Quick Trick: Init container exit code must be zero to proceed [OK]

Common Mistakes:

Master "Pods" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

Why does this Pod fail to start?