Dockerfile for microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Dockerfile in the context of microservices?

A Dockerfile is a simple text file that contains instructions to build a Docker image. For microservices, it defines how to package each service with its code, dependencies, and environment so it can run independently.

beginner

Why do microservices use Dockerfiles?

Microservices use Dockerfiles to create isolated, consistent environments for each service. This helps developers run, test, and deploy services independently without conflicts.

beginner

What is the purpose of the 'FROM' instruction in a Dockerfile?

The 'FROM' instruction sets the base image for the Docker image. It tells Docker which starting point to use, like a basic operating system or runtime environment needed for the microservice.

beginner

How does the 'COPY' instruction help in a Dockerfile for microservices?

The 'COPY' instruction copies files or folders from your local machine into the Docker image. This is how your microservice code and configuration files get included inside the container.

beginner

What does the 'CMD' instruction do in a Dockerfile?

The 'CMD' instruction specifies the command to run when the container starts. For microservices, it usually runs the service application so it begins listening for requests.

Which Dockerfile instruction sets the base image for a microservice?

A RUN

B COPY

C FROM

D CMD

The FROM instruction defines the base image for the Docker image.

What is the main purpose of a Dockerfile in microservices?

A To build a Docker image for each service

B To write the service code

C To deploy services to the cloud

D To monitor service health

Dockerfiles are used to build Docker images that package each microservice.

Which instruction copies your microservice code into the Docker image?

A COPY

B RUN

C EXPOSE

D ENV

COPY copies files from your local machine into the Docker image.

What does the CMD instruction do in a Dockerfile?

A Sets environment variables

B Copies files into the image

C Runs commands during image build

D Specifies the command to run when the container starts

CMD defines the command that runs when the container starts.

Why is it important to have a separate Dockerfile for each microservice?

A To avoid using Docker Compose

B To ensure each service runs in its own isolated environment

C To reduce the number of containers

D To combine all services into one container

Each microservice needs its own Dockerfile to run independently and avoid conflicts.

Explain the key instructions you would include in a Dockerfile for a simple microservice.

Think about how to build the image step-by-step.

Describe why Dockerfiles are essential for deploying microservices in containers.

Consider the benefits of packaging services with their dependencies.

Practice

1. What is the main purpose of a Dockerfile in a microservices project?

easy

A. To monitor the performance of the microservice

B. To write the microservice's business logic code

C. To define how to build a container image for the microservice

D. To deploy the microservice to the cloud

Solution

1. Step 1: Understand the role of Dockerfile

   A Dockerfile contains instructions to build a container image, including base image, dependencies, and commands.

2. Step 2: Differentiate from other tasks

   Writing code, monitoring, and deployment are separate tasks outside the Dockerfile's scope.

3. Final Answer:

   To define how to build a container image for the microservice -> Option C

4. Quick Check:

   Dockerfile = build container image [OK]

Hint: Dockerfile builds images, not code or deployment [OK]

Common Mistakes:

• Confusing Dockerfile with source code files
• Thinking Dockerfile handles deployment
• Assuming Dockerfile monitors services

2. Which of the following is the correct syntax to specify the base image in a Dockerfile?

easy

A. BASE python:3.12-slim

B. START python:3.12-slim

C. IMAGE python:3.12-slim

D. FROM python:3.12-slim

Solution

1. Step 1: Recall Dockerfile base image syntax

   The Dockerfile uses the FROM keyword to specify the base image.

2. Step 2: Verify other options

   BASE, IMAGE, and START are not valid Dockerfile instructions.

3. Final Answer:

   FROM python:3.12-slim -> Option D

4. Quick Check:

   Base image starts with FROM [OK]

Hint: Base image always starts with FROM in Dockerfile [OK]

Common Mistakes:

• Using incorrect keywords like BASE or IMAGE
• Forgetting the colon between image name and tag
• Writing lowercase FROM

3. Given this Dockerfile snippet:

FROM node:18-alpine
WORKDIR /app
COPY package.json ./
RUN npm install
COPY . .
CMD ["node", "server.js"]

What happens when you build and run this container?

medium

A. The container fails because WORKDIR is missing

B. The container runs the server.js file using Node.js

C. The container installs Python dependencies

D. The container runs npm start automatically

Solution

1. Step 1: Analyze Dockerfile commands

   The base image is Node.js 18 Alpine. It sets working directory to /app, copies package.json, runs npm install, copies all files, then runs node server.js.

2. Step 2: Understand container behavior

   On running, the container executes node server.js, starting the Node.js app. No Python involved. WORKDIR is present, so no failure.

3. Final Answer:

   The container runs the server.js file using Node.js -> Option B

4. Quick Check:

   CMD runs node server.js [OK]

Hint: CMD runs the specified command when container starts [OK]

Common Mistakes:

• Assuming Python dependencies install
• Thinking WORKDIR is missing
• Confusing CMD with npm start

4. Identify the error in this Dockerfile snippet for a Python microservice:

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

medium

A. The WORKDIR should be set before copying requirements.txt

B. The pip install command is missing the --user flag

C. The CMD syntax is incorrect

D. The base image version is invalid

Solution

1. Step 1: Check file paths and working directory order

   The requirements.txt is copied to /app/, but WORKDIR is set after. So pip install runs in root, not /app, causing file not found error.

2. Step 2: Correct order for Dockerfile commands

   Set WORKDIR /app before copying files and running commands to ensure correct paths.

3. Final Answer:

   The WORKDIR should be set before copying requirements.txt -> Option A

4. Quick Check:

   Set WORKDIR before file operations [OK]

Hint: Set WORKDIR before copying files and running commands [OK]

Common Mistakes:

• Running pip install before setting WORKDIR
• Misunderstanding CMD JSON syntax
• Assuming base image version is wrong

5. You want to optimize a Dockerfile for a Java microservice to reduce build time and image size. Which change is best to achieve this?

FROM openjdk:17
COPY . /app
WORKDIR /app
RUN ./gradlew build
CMD ["java", "-jar", "build/libs/app.jar"]

hard

A. Copy only build.gradle and settings.gradle first, run gradlew build, then copy the rest

B. Remove the WORKDIR instruction

C. Use CMD java -jar build/libs/app.jar without JSON array

D. Change base image to openjdk:8

Solution

1. Step 1: Understand Docker layer caching

   Docker caches layers. Copying only build files first and running build caches dependencies, so changes in source code don't rebuild dependencies.

2. Step 2: Apply multi-step copy for optimization

   Copy build.gradle and settings.gradle first, run gradlew build, then copy source files. This reduces rebuild time and image size.

3. Final Answer:

   Copy only build.gradle and settings.gradle first, run gradlew build, then copy the rest -> Option A

4. Quick Check:

   Optimize Dockerfile with layered caching [OK]

Hint: Copy build files first to leverage Docker cache [OK]

Common Mistakes:

• Removing WORKDIR breaks path context
• Using shell form CMD can cause signal issues
• Downgrading base image unnecessarily