Init containers in Kubernetes - Step-by-Step Execution

Process Flow - Init containers

Pod starts

↓

Init Container 1 runs

↓

Init Container 1 completes?

No→Wait

Yes↓

Init Container 2 runs

↓

Init Container 2 completes?

No→Wait

Yes↓

Main containers start

↓

Pod running

Init containers run one by one before main containers start. Each must finish successfully before the next begins.

Execution Sample

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: example-pod
spec:
  initContainers:
  - name: init-setup
    image: busybox
    command: ['sh', '-c', 'echo Init container running; sleep 3']
  containers:
  - name: main-app
    image: nginx

This pod runs an init container that prints a message and waits 3 seconds before starting the main nginx container.

Process Table

Step	Container	Action	Status	Next Step
1	init-setup	Start init container	Running	Wait for completion
2	init-setup	Complete command 'echo Init container running; sleep 3'	Succeeded	Start main-app container
3	main-app	Start main container nginx	Running	Pod is running
4	main-app	Container running normally	Running	Pod stays running

💡 Init container completed successfully, main container started, pod is running

Status Tracker

Container	Initial State	After Step 1	After Step 2	Final State
init-setup	Not started	Running	Succeeded	Completed
main-app	Not started	Not started	Running	Running

Key Moments - 2 Insights

Why does the main container not start immediately?

The execution_table shows the init container must complete successfully (Step 2) before the main container starts (Step 3). This ensures setup tasks finish first.

What happens if an init container fails?

If an init container fails, the pod will keep retrying that init container and will not start the main containers, as shown by the 'Wait for completion' action in Step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the status of 'init-setup' at Step 2?

A Succeeded

B Running

C Failed

D Not started

💡 Hint

Check the 'Status' column for Step 2 in the execution_table.

At which step does the main container start running?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for 'Start main container nginx' in the 'Action' column.

If the init container took longer to complete, which step would be delayed?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Main container starts only after init container succeeds (Step 3).

Concept Snapshot

Init containers run before main containers in a pod.
They run sequentially and must complete successfully.
Main containers start only after all init containers finish.
Used for setup tasks like config or waiting for services.
If an init container fails, pod startup pauses until fixed.

Full Transcript

Init containers are special containers in Kubernetes pods that run before the main containers start. They run one after another, and each must finish successfully before the next begins. This ensures setup tasks like configuration or waiting for resources complete first. In the example, the init container runs a simple command and waits 3 seconds. Only after it finishes does the main nginx container start. If an init container fails, the pod will keep retrying it and will not start the main containers until it succeeds.

Practice

1. What is the primary purpose of an init container in Kubernetes?

easy

A. To run setup tasks before the main application container starts

B. To replace the main application container

C. To monitor the health of the main container continuously

D. To scale the number of application containers automatically

Solution

1. Step 1: Understand the role of init containers

   Init containers run before the main app container to prepare the environment, such as setting up files or waiting for services.

2. Step 2: Compare options with this role

   Only To run setup tasks before the main application container starts describes running setup tasks before the main container starts, which matches the purpose of init containers.

3. Final Answer:

   To run setup tasks before the main application container starts -> Option A

4. Quick Check:

   Init container purpose = setup before main container [OK]

Hint: Init containers run first to prepare environment [OK]

Common Mistakes:

• Thinking init containers replace main containers
• Confusing init containers with health checks
• Assuming init containers handle scaling

2. Which of the following is the correct syntax to define an init container in a Kubernetes Pod spec?

easy

A. containers:
- name: init-example
image: busybox
initContainers:
- name: init-example
image: busybox

B. initContainers:
- name: init-example
image: busybox
containers:
- name: app
image: nginx

C. init:
- name: init-example
image: busybox
containers:
- name: app
image: nginx

D. containers:
- name: app
image: nginx
init:
- name: init-example
image: busybox

Solution

1. Step 1: Recall Kubernetes Pod spec structure

   Init containers are defined under the initContainers field, separate from containers.

2. Step 2: Identify correct syntax

   initContainers: - name: init-example image: busybox containers: - name: app image: nginx correctly places initContainers before containers with proper indentation and keys.

3. Final Answer:

   initContainers: - name: init-example image: busybox containers: - name: app image: nginx -> Option B

4. Quick Check:

   Init containers use 'initContainers' key [OK]

Hint: Use 'initContainers' key, not 'init' [OK]

Common Mistakes:

• Using 'init' instead of 'initContainers'
• Placing init container inside 'containers' list
• Incorrect indentation or YAML structure

3. Given this Pod spec snippet, what will happen when the Pod starts?

initContainers:
- name: wait-for-db
  image: busybox
  command: ['sh', '-c', 'until nslookup db-service; do echo waiting; sleep 2; done']
containers:
- name: app
  image: myapp

medium

A. The init container runs in parallel with the app container

B. The app container starts immediately without waiting

C. The Pod fails because 'nslookup' is not a valid command

D. The init container waits until 'db-service' DNS resolves before app starts

Solution

1. Step 1: Understand init container behavior

   Init containers run before app containers and must complete successfully before the app starts.

2. Step 2: Analyze the command in init container

   The command loops until the DNS name 'db-service' resolves, so it waits for the database service to be ready.

3. Final Answer:

   The init container waits until 'db-service' DNS resolves before app starts -> Option D

4. Quick Check:

   Init container waits for service readiness [OK]

Hint: Init containers run sequentially and block app start [OK]

Common Mistakes:

• Thinking init containers run in parallel
• Assuming app starts immediately
• Believing 'nslookup' is invalid in busybox

4. You defined an init container but your main app container never starts. What is the most likely cause?

medium

A. The Pod spec is missing the 'containers' section

B. The app container image is missing

C. The init container failed or is stuck and did not complete successfully

D. The init container is running after the app container

Solution

1. Step 1: Recall init container lifecycle

   Init containers must complete successfully before the app container starts.

2. Step 2: Identify why app container never starts

   If the init container fails or hangs, the app container will not start, causing the Pod to stall.

3. Final Answer:

   The init container failed or is stuck and did not complete successfully -> Option C

4. Quick Check:

   Init container failure blocks app start [OK]

Hint: Check init container status if app never starts [OK]

Common Mistakes:

• Ignoring init container failure status
• Assuming app container image issues cause this
• Thinking init containers run after app containers

5. You want to use multiple init containers to prepare your Pod environment: one to create a config file, and another to download data. How does Kubernetes handle their execution?

hard

A. Init containers run sequentially, one after another, before the app starts

B. Init containers run after the app container starts

C. Only the first init container runs; others are ignored

D. All init containers run in parallel, and the app starts when all finish

Solution

1. Step 1: Understand init container execution order

   Kubernetes runs init containers one by one, in the order defined, waiting for each to finish before starting the next.

2. Step 2: Confirm app container start timing

   The app container only starts after all init containers have completed successfully.

3. Final Answer:

   Init containers run sequentially, one after another, before the app starts -> Option A

4. Quick Check:

   Init containers run sequentially before app [OK]

Hint: Init containers run one by one before app starts [OK]

Common Mistakes:

• Assuming init containers run in parallel
• Thinking app starts before init containers finish
• Believing only the first init container runs