Why Docker in CI/CD matters - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to build a Docker image named 'app' from the current directory.

Docker

docker build -t app [1] Dockerfile .

Drag options to blanks, or click blank then click option'

A-d

B-f

C-p

D-t

Attempts:

3 left

💡 Hint

Common Mistakes

Using -d which runs containers detached, not for building images.

The -f option specifies the Dockerfile to use. Here, it points to the current directory's Dockerfile.

2fill in blank

medium

Complete the command to run a Docker container named 'web' in detached mode.

Docker

docker run --name web [1] nginx

Drag options to blanks, or click blank then click option'

A-it

B-rm

C-p

D-d

Attempts:

3 left

💡 Hint

Common Mistakes

Using -it which runs the container interactively.

The -d option runs the container in detached mode, meaning it runs in the background.

3fill in blank

hard

Fix the error in the command to push the Docker image 'app' to Docker Hub.

Docker

docker push [1]/app

Drag options to blanks, or click blank then click option'

Ausername

Bapp

Clatest

Ddocker

Attempts:

3 left

💡 Hint

Common Mistakes

Pushing without username causes 'repository not found' errors.

You must prefix the image name with your Docker Hub username to push it correctly.

4fill in blank

hard

Fill both blanks to create a Dockerfile that uses the 'python:3.12' image and copies 'app.py' into the container.

Docker

FROM [1]
COPY [2] /app.py

Drag options to blanks, or click blank then click option'

Apython:3.12

Bapp.py

Cnginx:latest

Drequirements.txt

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong base image or copying wrong files.

The FROM line sets the base image. The COPY line copies the local app.py file into the container.

5fill in blank

hard

Fill all three blanks to define a Docker Compose service named 'web' that builds from the current directory, maps port 5000, and restarts always.

Docker

services:
  web:
    build: [1]
    ports:
      - "[2]:5000"
    restart: [3]

Drag options to blanks, or click blank then click option'

A.

B5000

Calways

Dnever

Attempts:

3 left

💡 Hint

Common Mistakes

Wrong build path, incorrect port mapping, or wrong restart policy.

The build path is current directory .. The port mapping exposes port 5000. The restart policy always restarts the container if it stops.

Practice

1. Why is Docker important in a CI/CD pipeline?

easy

A. It slows down the deployment process.

B. It replaces the need for version control systems.

C. It creates consistent environments for building and testing code.

D. It automatically writes code for developers.

Solution

1. Step 1: Understand Docker's role in environment consistency

   Docker packages applications with their environment, ensuring the same setup everywhere.

2. Step 2: Connect environment consistency to CI/CD benefits

   This consistency avoids errors caused by differences between developer and production setups.

3. Final Answer:

   It creates consistent environments for building and testing code. -> Option C

4. Quick Check:

   Docker ensures consistent environments = D [OK]

Hint: Docker equals consistent environments in CI/CD [OK]

Common Mistakes:

• Thinking Docker replaces version control
• Believing Docker writes code automatically
• Assuming Docker slows deployment

2. Which Docker command is used to build an image in a CI/CD pipeline?

easy

A. docker build

B. docker run

C. docker push

D. docker commit

Solution

1. Step 1: Identify the command to create Docker images

   The docker build command creates an image from a Dockerfile.

2. Step 2: Differentiate from other Docker commands

   docker run starts containers, docker push uploads images, and docker commit saves container changes as images.

3. Final Answer:

   docker build -> Option A

4. Quick Check:

   Build image = docker build [OK]

Hint: Build images with 'docker build' command [OK]

Common Mistakes:

• Using 'docker run' to build images
• Confusing 'docker push' with build
• Thinking 'docker commit' builds images

3. Given this Dockerfile snippet in a CI/CD pipeline:

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

What happens when the image runs?

medium

A. It installs Python 3.12 and runs app.py automatically.

B. It copies files but does not install dependencies.

C. It runs app.py without installing dependencies.

D. It fails because the WORKDIR is missing.

Solution

1. Step 1: Analyze the Dockerfile commands

   The image uses Python 3.12, copies files to /app, sets /app as working directory, installs dependencies, and sets the command to run app.py.

2. Step 2: Understand the effect when running the container

   When started, the container runs python app.py with dependencies installed.

3. Final Answer:

   It installs Python 3.12 and runs app.py automatically. -> Option A

4. Quick Check:

   Dockerfile installs dependencies and runs app.py = A [OK]

Hint: RUN installs, CMD runs app [OK]

Common Mistakes:

• Ignoring RUN command effects
• Assuming WORKDIR is missing
• Thinking dependencies are not installed

4. In a CI/CD pipeline, a Docker build fails with this error:
ERROR: failed to solve with frontend dockerfile.v0: failed to read dockerfile: open Dockerfile: no such file or directory
What is the most likely cause?

medium

A. The image name is invalid.

B. The Docker daemon is not running.

C. The Dockerfile has syntax errors.

D. The Dockerfile is missing or not in the build context directory.

Solution

1. Step 1: Interpret the error message

   The error says Docker cannot find the Dockerfile to read it.

2. Step 2: Identify common reasons for missing Dockerfile

   Usually, the Dockerfile is missing or not located in the directory where the build command runs.

3. Final Answer:

   The Dockerfile is missing or not in the build context directory. -> Option D

4. Quick Check:

   Missing Dockerfile = C [OK]

Hint: Check Dockerfile location if build fails [OK]

Common Mistakes:

• Assuming daemon is stopped without checking
• Blaming image name for Dockerfile errors
• Confusing syntax errors with missing file

5. How does using Docker in CI/CD pipelines improve software delivery speed and reliability?

hard

A. By automatically generating deployment scripts without human input.

B. By creating isolated, consistent environments that avoid "works on my machine" errors.

C. By replacing all manual testing with automated code generation.

D. By requiring developers to install all dependencies manually on each machine.

Solution

1. Step 1: Understand Docker's environment isolation

   Docker packages apps with their dependencies, creating identical environments everywhere.

2. Step 2: Connect environment consistency to faster, reliable delivery

   This avoids errors caused by different setups, reducing debugging and speeding delivery.

3. Final Answer:

   By creating isolated, consistent environments that avoid "works on my machine" errors. -> Option B

4. Quick Check:

   Docker isolates environments = faster, reliable delivery [OK]

Hint: Docker avoids environment errors for faster delivery [OK]

Common Mistakes:

• Thinking Docker auto-generates deployment scripts
• Believing Docker replaces manual testing
• Assuming manual dependency installs are needed