Consistent environments across teams in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Docker command?

You run the command docker run --rm alpine echo Hello World. What will be the output?

Docker

docker run --rm alpine echo Hello World

A Error: command not found

B alpine: Hello World

C Hello World

D Container started but no output

💡 Hint

Think about what the echo command does inside the container.

The command runs an Alpine Linux container, executes echo Hello World, which prints 'Hello World' and then the container stops and is removed due to --rm.

❓ Configuration

intermediate

Which Dockerfile snippet ensures consistent environment by fixing the base image version?

You want to make sure your Docker image always uses the same base environment. Which Dockerfile line achieves this?

A FROM ubuntu:rolling

B FROM ubuntu:latest

C FROM ubuntu

D FROM ubuntu:20.04

💡 Hint

Using a specific version tag helps avoid unexpected changes.

Using 'ubuntu:20.04' fixes the base image to a specific version, ensuring consistent environment across builds. 'ubuntu' or 'ubuntu:latest' can change over time, causing inconsistencies.

🔀 Workflow

advanced

What is the correct order to build and share a Docker image for team use?

Arrange these steps in the correct order to build a Docker image and share it with your team.

A 3,1,2,4

B 1,3,2,4

C 1,2,3,4

D 3,2,1,4

💡 Hint

You must authenticate before pushing images.

First, login to Docker registry (3), then build the image (1), push it (2), and finally team members pull it (4).

❓ Troubleshoot

advanced

Why does this Docker container fail to start consistently on different machines?

A Docker container built on one machine runs fine there but fails on another with missing dependencies error. What is the most likely cause?

A The Dockerfile uses a fixed base image version

B The container relies on host machine libraries not included in the image

C The container was built with multi-stage builds

D The container uses environment variables set inside the Dockerfile

💡 Hint

Containers should be self-contained.

If the container depends on host libraries, it won't run consistently on other machines. Images must include all dependencies.

✅ Best Practice

expert

Which practice best ensures consistent environments across teams using Docker?

Choose the best practice that helps teams avoid environment differences when using Docker containers.

A Pin exact versions of base images and dependencies in Dockerfiles and share images via a registry

B Build images locally on each developer machine without sharing

C Use 'latest' tag for base images to get newest updates automatically

D Rely on host OS to provide dependencies to containers

💡 Hint

Think about reproducibility and sharing.

Pinning versions and sharing images via a registry ensures everyone uses the same environment, avoiding surprises.

Practice

1. Why is Docker useful for maintaining consistent environments across teams?

easy

A. It packages the app and its environment together in a container.

B. It automatically writes code for the team.

C. It replaces the need for version control systems.

D. It runs apps only on Windows machines.

Solution

1. Step 1: Understand Docker container purpose

   Docker containers bundle the app with all its dependencies and environment settings.

2. Step 2: Compare options to Docker's role

   Only the option stating "It packages the app and its environment together in a container." describes packaging app and environment together, ensuring consistency.

3. Final Answer:

   It packages the app and its environment together in a container. -> Option A

4. Quick Check:

   Docker = consistent app environment [OK]

Hint: Docker bundles app + environment for all team members [OK]

Common Mistakes:

• Thinking Docker writes code automatically
• Confusing Docker with version control
• Believing Docker only works on Windows

2. Which of the following is the correct way to start a Docker container named webapp from an image called myapp:latest?

easy

A. docker build webapp myapp:latest

B. docker start myapp:latest webapp

C. docker create webapp myapp:latest

D. docker run --name webapp myapp:latest

Solution

1. Step 1: Recall Docker run syntax

   The command to start a container with a name is: docker run --name [container_name] [image]

2. Step 2: Match the correct command

   docker run --name webapp myapp:latest matches this syntax exactly, starting container 'webapp' from image 'myapp:latest'.

3. Final Answer:

   docker run --name webapp myapp:latest -> Option D

4. Quick Check:

   docker run --name = start container with name [OK]

Hint: Use 'docker run --name' to start named container [OK]

Common Mistakes:

• Using 'docker start' to create container
• Confusing 'docker create' with 'docker run'
• Using 'docker build' to start containers

3. Given this Dockerfile snippet:

FROM python:3.12-slim
WORKDIR /app
COPY . /app
RUN pip install -r requirements.txt
CMD ["python", "app.py"]

What happens when you build and run this Docker image on different team members' machines?

medium

A. The app runs only if all team members have Python installed locally.

B. The app will fail because Python versions differ on each machine.

C. Each team member runs the app in the exact same environment regardless of their OS.

D. The app runs slower on Windows than Linux due to Docker limitations.

Solution

1. Step 1: Analyze Dockerfile purpose

   The Dockerfile sets up a Python 3.12 environment inside a container, independent of host OS.

2. Step 2: Understand container consistency

   Because the container includes Python and dependencies, all team members get the same environment.

3. Final Answer:

   Each team member runs the app in the exact same environment regardless of their OS. -> Option C

4. Quick Check:

   Docker container = consistent environment [OK]

Hint: Dockerfile builds same environment on all machines [OK]

Common Mistakes:

• Assuming local Python is needed
• Believing OS affects container environment
• Thinking Docker slows app on Windows

4. A team member runs docker run myapp but gets an error: Cannot find image 'myapp' locally. What is the likely cause and fix?

medium

A. Docker is not installed; install Docker to fix this.

B. The image 'myapp' is not built locally; run docker build -t myapp . first.

C. The container name is missing; add --name myapp to the command.

D. The Dockerfile is missing; create a Dockerfile to fix this.

Solution

1. Step 1: Understand error meaning

   The error means Docker cannot find the image 'myapp' locally or on Docker Hub.

2. Step 2: Identify fix

   Building the image locally with docker build -t myapp . creates the image for use.

3. Final Answer:

   The image 'myapp' is not built locally; run docker build -t myapp . first. -> Option B

4. Quick Check:

   Image missing? Build it first [OK]

Hint: Build image before running container [OK]

Common Mistakes:

• Thinking Docker is not installed
• Confusing container name with image name
• Assuming Dockerfile absence causes this error

5. Your team wants to ensure everyone uses the same database version inside Docker containers. Which approach best guarantees this consistency?

hard

A. Create a Docker Compose file specifying the exact database image version and share it with the team.

B. Ask each team member to install the database manually on their machine.

C. Use environment variables to let each member choose their preferred database version.

D. Run the database directly on the host OS instead of in Docker.

Solution

1. Step 1: Understand Docker Compose role

   Docker Compose lets you define multi-container setups with exact image versions in one file.

2. Step 2: Evaluate options for consistency

   Sharing a Compose file with fixed database image version ensures all run the same version easily.

3. Step 3: Reject other options

   Manual installs or letting members choose versions cause inconsistency; running on host loses container benefits.

4. Final Answer:

   Create a Docker Compose file specifying the exact database image version and share it with the team. -> Option A

5. Quick Check:

   Compose file = consistent multi-container setup [OK]

Hint: Use Docker Compose with fixed image versions [OK]

Common Mistakes:

• Relying on manual installs for consistency
• Allowing different versions via environment variables
• Running services outside Docker containers