Common container startup failures in Docker - Mini Project: Build & Apply

Common Container Startup Failures

📖 Scenario: You are working as a DevOps engineer managing Docker containers for a web application. Sometimes containers fail to start due to common issues like missing environment variables, incorrect commands, or port conflicts. Understanding these failures helps you fix problems quickly and keep the application running smoothly.

🎯 Goal: Build a simple Docker container setup that demonstrates common startup failures and learn how to identify and fix them by checking logs and container status.

📋 What You'll Learn

Create a Dockerfile with a simple command

Add an environment variable configuration

Run the container with a command that may fail

Check and print container logs to identify startup issues

💡 Why This Matters

🌍 Real World

Containers often fail to start due to simple mistakes like wrong commands or missing environment variables. Knowing how to check logs and fix these helps keep applications running.

💼 Career

DevOps engineers and site reliability engineers regularly troubleshoot container startup issues to maintain uptime and reliability.

1

Create a Dockerfile with a simple command

Create a file named Dockerfile with the following content exactly: FROM alpine and CMD ["echo", "Hello World"].

Docker

# Create a Dockerfile with FROM alpine and CMD ["echo", "Hello World"]
# Your code here

Hint

Use the FROM instruction to specify the base image and CMD to set the command that runs when the container starts.

2

Add an environment variable configuration

Add an environment variable GREETING with value Hello Docker to the Dockerfile using the ENV instruction below the FROM alpine line.

Docker

FROM alpine
# Add ENV GREETING Hello Docker below
# Your code here
CMD ["echo", "Hello World"]

Hint

The ENV instruction sets environment variables inside the container.

3

Change the command to use the environment variable

Modify the CMD line to CMD ["sh", "-c", "echo $GREETING"] so the container prints the environment variable when it starts.

Docker

FROM alpine
ENV GREETING Hello Docker
# Change CMD to use echo $GREETING
# Your code here

Hint

Use sh -c to run shell commands that can access environment variables.

4

Run the container and check logs for startup issues

Run the container with the image you built using docker run --name test_container your_image_name. Then use docker logs test_container to print the container output and verify it shows Hello Docker.

Docker

# Run the container and print logs
# Your code here

Hint

Use docker logs to see what the container printed when it started.

Practice

1. What is a common reason a Docker container might fail to start immediately after running docker run?

easy

A. The container tries to use a port already in use on the host

B. The Docker daemon is running

C. The container image is very large

D. The host has enough free disk space

Solution

1. Step 1: Understand port conflicts in Docker

   If a container tries to bind to a port already used by another process on the host, it cannot start because the port is busy.

2. Step 2: Check other options for relevance

   Options B, C, and D do not prevent container startup immediately; only port conflict causes failure here.

3. Final Answer:

   The container tries to use a port already in use on the host -> Option A

4. Quick Check:

   Port conflict = container startup failure [OK]

Hint: Check if the port is free before starting container [OK]

Common Mistakes:

• Assuming large image size stops container start
• Thinking Docker daemon running causes failure
• Ignoring port conflicts

2. Which of the following docker run commands will correctly set an environment variable named APP_ENV to production?

easy

A. docker run --env APP_ENV production myimage

B. docker run -e APP_ENV production myimage

C. docker run -env APP_ENV=production myimage

D. docker run -e APP_ENV=production myimage

Solution

1. Step 1: Recall correct syntax for environment variables

   The correct flag is -e or --env followed by VAR=VALUE without spaces.

2. Step 2: Analyze each option

   docker run -e APP_ENV=production myimage uses correct syntax: -e APP_ENV=production. Options A, C, and D have syntax errors or missing '=' sign.

3. Final Answer:

   docker run -e APP_ENV=production myimage -> Option D

4. Quick Check:

   Use -e VAR=VALUE for env vars [OK]

Hint: Use -e VAR=VALUE with no spaces for env vars [OK]

Common Mistakes:

• Omitting '=' between variable and value
• Using incorrect flag like -env
• Adding spaces between variable and value

3. Given this command:

docker run -p 8080:80 nginx

What will happen if port 8080 on the host is already used by another service?

medium

A. Docker will automatically choose a different host port

B. The container will fail to start with a port binding error

C. The container will start normally and ignore the port conflict

D. The container will start but the service inside will not work

Solution

1. Step 1: Understand port binding behavior

   If the host port (8080) is already in use, Docker cannot bind the container port to it, causing failure.

2. Step 2: Evaluate other options

   Docker does not auto-select ports unless specified with -P. The container won't start ignoring conflicts or silently fail.

3. Final Answer:

   The container will fail to start with a port binding error -> Option B

4. Quick Check:

   Port in use causes start failure [OK]

Hint: Check host ports before binding with -p [OK]

Common Mistakes:

• Assuming Docker auto-changes ports
• Thinking container starts ignoring conflicts
• Believing service inside fails but container runs

4. You run a container with docker run -v /host/data:/app/data myimage but the container fails to start. What is the most likely cause?

medium

A. The image name is incorrect

B. The container does not have enough CPU resources

C. The host directory /host/data does not exist or has wrong permissions

D. The Docker daemon is not running

Solution

1. Step 1: Understand volume mount requirements

   Docker requires the host directory to exist and be accessible for volume mounts; otherwise, container startup fails.

2. Step 2: Check other options

   Incorrect image name causes image pull errors, not volume mount failure. CPU or daemon issues cause different errors.

3. Final Answer:

   The host directory /host/data does not exist or has wrong permissions -> Option C

4. Quick Check:

   Volume mount fails if host path missing [OK]

Hint: Verify host path exists and permissions before mounting [OK]

Common Mistakes:

• Ignoring host directory existence
• Confusing image name errors with volume errors
• Assuming CPU limits cause mount failures

5. You have a container that fails immediately after starting. You run docker logs container_id and see an error about a missing environment variable DB_HOST. How should you fix this?

hard

A. Add -e DB_HOST=value to the docker run command

B. Increase the container's CPU and memory limits

C. Change the container image to a different one

D. Restart the container without changes

Solution

1. Step 1: Interpret the error message from logs

   The logs indicate the container expects an environment variable DB_HOST which is missing, causing failure.

2. Step 2: Provide the missing environment variable

   Use -e DB_HOST=value in the docker run command to supply the required variable.

3. Step 3: Understand why other options fail

   Restarting without changes won't fix missing vars. Changing image or resources doesn't address environment variables.

4. Final Answer:

   Add -e DB_HOST=value to the docker run command -> Option A

5. Quick Check:

   Missing env var fixed by -e flag [OK]

Hint: Use docker logs to find missing env vars, then add -e [OK]

Common Mistakes:

• Restarting without fixing environment variables
• Changing image unnecessarily
• Increasing resources instead of fixing config