Init container pattern in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Init Containers in Kubernetes

What is the main purpose of using an init container in a Kubernetes Pod?

A To provide a user interface for the application

B To run setup tasks before the main application container starts

C To scale the number of application containers automatically

D To replace the main application container after it crashes

💡 Hint

Think about tasks that must finish before the main app runs.

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

💻 Command Output

intermediate

Output of Init Container Status

Given the following kubectl get pod mypod -o json snippet showing init container status, what is the state of the init container?

{
  "status": {
    "initContainerStatuses": [
      {
        "name": "init-setup",
        "state": {
          "terminated": {
            "exitCode": 0,
            "reason": "Completed"
          }
        }
      }
    ]
  }
}

A Init container finished successfully

B Init container is still running

C Init container failed to start

D Init container was skipped

💡 Hint

Look at the exitCode and reason fields.

The init container terminated with exit code 0 and reason 'Completed', meaning it finished successfully.

❓ Configuration

advanced

Correct Init Container YAML Configuration

Which YAML snippet correctly defines an init container that copies files from a shared volume before the main container starts?

A

initContainers:
  - name: init-copy
    image: busybox
    command: ['sh', '-c', 'cp /source/* /dest/']
    volumeMounts:
      - name: shared-data
        mountPath: /dest
containers:
  - name: app
    image: myapp
    volumeMounts:
      - name: shared-data
        mountPath: /app/data
volumes:
  - name: shared-data
    emptyDir: {}

B

initContainers:
  - name: init-copy
    image: busybox
    command: ['sh', '-c', 'cp /source/* /dest/']
containers:
  - name: app
    image: myapp
volumes:
  - name: shared-data
    emptyDir: {}

C

initContainers:
  - name: init-copy
    image: busybox
    command: ['cp', '/source/*', '/dest/']
    volumeMounts:
      - name: shared-data
        mountPath: /dest
containers:
  - name: app
    image: myapp
    volumeMounts:
      - name: shared-data
        mountPath: /app/data
volumes:
  - name: shared-data
    emptyDir: {}

D

containers:
  - name: init-copy
    image: busybox
    command: ['sh', '-c', 'cp /source/* /dest/']
    volumeMounts:
      - name: shared-data
        mountPath: /dest
initContainers:
  - name: app
    image: myapp
    volumeMounts:
      - name: shared-data
        mountPath: /app/data
volumes:
  - name: shared-data
    emptyDir: {}

💡 Hint

Check the placement of initContainers and volume mounts.

Option A correctly places the init container under initContainers, uses a shell command to copy files, and mounts the shared volume in both containers.

❓ Troubleshoot

advanced

Init Container Fails to Complete

You have an init container that never completes and blocks the main container from starting. Which of the following is the most likely cause?

A The Kubernetes node is out of disk space

B The main container image is missing

C The pod has no resource limits set

D The init container command is stuck waiting for input or a service that is not available

💡 Hint

Think about what can cause a container to hang during startup.

If the init container command waits indefinitely (e.g., for input or a service), it will block the pod from progressing.

🔀 Workflow

expert

Init Container Execution Order

Consider a Pod with three init containers named init1, init2, and init3. Which statement correctly describes their execution order?

A They run randomly and independently of order

B They run in parallel and the Pod starts when all finish

C They run sequentially in the order defined in the Pod spec, each must complete before the next starts

D Only the first init container runs; the others run only if the first fails

💡 Hint

Think about how Kubernetes ensures setup tasks complete before the app runs.

Init containers run one after another in the order they appear in the Pod spec. Each must finish successfully before the next starts.

Practice

1. What is the main purpose of an init container in Docker or Kubernetes?

easy

A. To run setup tasks before the main application starts

B. To replace the main application container

C. To run the main application continuously

D. To monitor the main container's logs

Solution

1. Step 1: Understand init container role

   Init containers run before the main container to prepare the environment.

2. Step 2: Compare options

   Only To run setup tasks before the main application starts describes running setup tasks before the main app starts, which is the init container's job.

3. Final Answer:

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

4. Quick Check:

   Init container purpose = run setup tasks before main app [OK]

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

Common Mistakes:

• Thinking init containers replace main containers
• Assuming init containers run continuously
• Confusing init containers with monitoring tools

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

easy

A. initContainers:
- name: init
image: busybox
command: ['sh', '-c', 'echo Init']

B. containers:
- name: init
image: busybox
command: ['sh', '-c', 'echo Init']

C. init:
- name: init
image: busybox
command: ['sh', '-c', 'echo Init']

D. preContainers:
- name: init
image: busybox
command: ['sh', '-c', 'echo Init']

Solution

1. Step 1: Recall Kubernetes Pod spec structure

   Init containers are defined under the initContainers field in the Pod spec.

2. Step 2: Match correct YAML key

   Only initContainers: - name: init image: busybox command: ['sh', '-c', 'echo Init'] uses initContainers correctly; others use invalid keys.

3. Final Answer:

   initContainers with proper container spec -> Option A

4. Quick Check:

   Init containers key = initContainers [OK]

Hint: Init containers use 'initContainers' key in Pod YAML [OK]

Common Mistakes:

• Using 'containers' instead of 'initContainers'
• Using invalid keys like 'init' or 'preContainers'
• Misplacing init container definition outside Pod spec

3. Given this Pod spec snippet, what will happen if the init container fails?

initContainers:
  - name: setup
    image: busybox
    command: ['sh', '-c', 'exit 1']
containers:
  - name: app
    image: nginx

medium

A. The main app container will start normally

B. The Pod will ignore the init container failure and continue

C. The Pod will restart the init container until it succeeds

D. The main app container will start but with errors

Solution

1. Step 1: Understand init container failure behavior

   If an init container fails, Kubernetes restarts it until it succeeds or the Pod is stopped.

2. Step 2: Analyze options

   Only The Pod will restart the init container until it succeeds correctly states the Pod restarts the init container on failure; main container won't start until success.

3. Final Answer:

   The Pod will restart the init container until it succeeds -> Option C

4. Quick Check:

   Init container failure = Pod restarts init container [OK]

Hint: Init container failure causes restart, blocks main container [OK]

Common Mistakes:

• Thinking main container starts despite init failure
• Assuming Pod ignores init container failure
• Believing main container runs with errors from init failure

4. You wrote this Pod YAML but the init container does not run before the main container:

containers:
  - name: app
    image: nginx
initContainers:
  - name: setup
    image: busybox
    command: ['sh', '-c', 'echo Setup']

What is the likely error?

medium

A. The initContainers section is placed after containers, order matters

B. The initContainers key is incorrectly indented or misplaced

C. The command syntax is invalid for init containers

D. The image busybox cannot be used as an init container

Solution

1. Step 1: Check YAML structure rules

   Init containers must be correctly indented and placed at the same level as containers under the Pod spec.

2. Step 2: Identify common YAML mistakes

   Misplaced or wrongly indented initContainers causes it to be ignored, so init container won't run.

3. Final Answer:

   The initContainers key is incorrectly indented or misplaced -> Option B

4. Quick Check:

   YAML indentation errors cause init container not to run [OK]

Hint: Check YAML indentation and placement for initContainers [OK]

Common Mistakes:

• Assuming order of keys matters in YAML
• Using wrong command syntax inside init container
• Believing image choice blocks init container

5. You want to use an init container to download a configuration file before your main app starts. Which approach correctly shares the file between the init container and the main container?

hard

A. Copy the file from init container to main container using Docker cp command

B. Run the init container after the main container starts to copy the file

C. Store the file inside the init container image and expect main container to access it

D. Use a shared emptyDir volume mounted in both init and main containers

Solution

1. Step 1: Understand file sharing between containers

   Containers in the same Pod can share files using a shared volume like emptyDir.

2. Step 2: Evaluate options for sharing files

   Only Use a shared emptyDir volume mounted in both init and main containers correctly uses a shared volume mounted in both containers to share files.

3. Final Answer:

   Use a shared emptyDir volume mounted in both init and main containers -> Option D

4. Quick Check:

   Shared volume = file sharing between init and main containers [OK]

Hint: Use shared volume like emptyDir for file sharing [OK]

Common Mistakes:

• Trying to copy files between containers manually
• Expecting files inside init container image to be accessible
• Running init container after main container starts