Reducing image size strategies in Docker - Step-by-Step Execution

Process Flow - Reducing image size strategies

Start with Base Image

↓

Minimize Layers

↓

Use .dockerignore

↓

Remove Unnecessary Files

↓

Use Multi-stage Builds

↓

Choose Minimal Base Images

↓

Final Small Image

This flow shows the steps to reduce Docker image size by starting with a base image and applying strategies like minimizing layers, ignoring files, cleaning up, using multi-stage builds, and choosing minimal base images.

Execution Sample

Docker

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

This Dockerfile copies app files, installs dependencies, removes test files to reduce image size, and runs the app.

Process Table

Step	Action	Effect on Image Size	Details
1	Start with python:3.12-slim base image	Small base size	Uses slim variant to reduce base image size
2	COPY . /app	Adds app files	Copies all files, including unnecessary ones if no .dockerignore
3	RUN pip install -r /app/requirements.txt	Adds dependencies	Installs required packages, increases size
4	RUN rm -rf /app/tests	Removes test files	Deletes unnecessary test files to reduce size
5	CMD ["python", "/app/app.py"]	No size change	Sets container start command
6	Use .dockerignore to exclude files	Prevents copying unwanted files	Reduces size by ignoring docs, configs, etc.
7	Use multi-stage build	Final image smaller	Build dependencies removed in final stage
8	Choose minimal base image	Base image smaller	E.g., alpine instead of full python image
9	Exit	Image size minimized	All strategies applied

💡 All steps applied to reduce Docker image size effectively

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Image Size	Base image size (~50MB)	Base + app files (~70MB)	After dependencies (~150MB)	After removing tests (~140MB)	Final optimized size (~100MB)

Key Moments - 3 Insights

Why does removing files in a RUN command reduce image size?

Because each RUN creates a new layer, removing files in the same RUN step avoids adding extra size from previous layers. See execution_table step 4 where rm -rf reduces size.

How does .dockerignore help reduce image size?

.dockerignore prevents unwanted files from being copied into the image at all, so they never add to the image size. Refer to execution_table step 6.

What is the benefit of multi-stage builds?

Multi-stage builds allow you to copy only the final needed artifacts into the last image, leaving build tools and dependencies behind, reducing final image size. See execution_table step 7.

Visual Quiz - 3 Questions

Look at the execution table, after which step does the image size decrease?

A After step 3 (install dependencies)

B After step 2 (copy files)

C After step 4 (remove test files)

D After step 5 (set CMD)

💡 Hint

Check the 'Effect on Image Size' column for step 4 in the execution_table.

According to variable_tracker, what is the approximate image size after installing dependencies?

A ~150MB

B ~50MB

C ~70MB

D ~100MB

💡 Hint

Look at 'After Step 3' column for 'Image Size' in variable_tracker.

If you add more files but use .dockerignore properly, what happens to the image size?

A Image size increases significantly

B Image size stays smaller by ignoring files

C Image size doubles

D Image size is unaffected by .dockerignore

💡 Hint

Refer to execution_table step 6 about .dockerignore effect.

Concept Snapshot

Reducing Docker image size:
- Use minimal base images (e.g., slim, alpine)
- Minimize layers by combining RUN commands
- Use .dockerignore to exclude files
- Remove unnecessary files in same RUN step
- Use multi-stage builds to separate build and runtime
- Result: smaller, faster, efficient images

Full Transcript

This visual execution shows how to reduce Docker image size step-by-step. We start with a minimal base image, then copy application files. Installing dependencies adds size, but removing unnecessary files like tests reduces it. Using .dockerignore prevents copying unwanted files, keeping the image smaller. Multi-stage builds help by separating build tools from the final image. Choosing minimal base images like slim or alpine also reduces size. Tracking image size after each step shows how these strategies combine to create a smaller, efficient Docker image.

Practice

1. Which of the following is the best initial step to reduce the size of a Docker image?

easy

A. Start with a small base image like Alpine or slim variants

B. Install all available packages to avoid missing dependencies

C. Use the latest Ubuntu image without modifications

D. Add unnecessary files to the image for future use

Solution

1. Step 1: Understand base image impact

   The base image sets the starting size; smaller bases mean smaller final images.

2. Step 2: Compare options

   Alpine and slim variants are minimal, unlike full Ubuntu or adding unnecessary files.

3. Final Answer:

   Start with a small base image like Alpine or slim variants -> Option A

4. Quick Check:

   Small base image = smaller Docker image [OK]

Hint: Choose minimal base images first to reduce size [OK]

Common Mistakes:

• Using full OS images without slimming
• Installing unnecessary packages
• Adding extra files without need

2. Which Dockerfile command sequence correctly cleans up package manager caches to reduce image size?

easy

A. RUN apt-get update && rm -rf /var/lib/apt/lists/* && apt-get install curl

B. RUN apt-get install curl && apt-get update

C. RUN rm -rf /var/lib/apt/lists/* && apt-get install curl

D. RUN apt-get update && apt-get install -y curl && rm -rf /var/lib/apt/lists/*

Solution

1. Step 1: Understand package installation order

   First update package lists, then install packages, finally clean cache to reduce image size.

2. Step 2: Analyze commands

   RUN apt-get update && apt-get install -y curl && rm -rf /var/lib/apt/lists/* updates, installs, then removes cache correctly; others have wrong order causing errors or no cleanup.

3. Final Answer:

   RUN apt-get update && apt-get install -y curl && rm -rf /var/lib/apt/lists/* -> Option D

4. Quick Check:

   Update -> install -> clean cache = correct order [OK]

Hint: Update before install, clean cache after install [OK]

Common Mistakes:

• Cleaning cache before installing packages
• Skipping apt-get update
• Wrong command order causing errors

3. Given this Dockerfile snippet, what will be the approximate size effect on the final image?

FROM node:18-alpine
RUN apk add --no-cache git
COPY . /app
RUN npm install

medium

A. The image will be small because Alpine and --no-cache reduce size

B. The image will be large because npm install always adds big size

C. The image will be large because git is installed without cache cleanup

D. The image size is unaffected by base image or package installs

Solution

1. Step 1: Analyze base image and package install

   Using Alpine base and apk with --no-cache avoids cache files, keeping image small.

2. Step 2: Consider npm install impact

   npm install adds dependencies but starting from Alpine keeps overall size smaller than heavier bases.

3. Final Answer:

   The image will be small because Alpine and --no-cache reduce size -> Option A

4. Quick Check:

   Alpine + --no-cache = smaller image [OK]

Hint: Use Alpine + --no-cache to keep image small [OK]

Common Mistakes:

• Assuming npm install always makes image large
• Ignoring --no-cache effect
• Not considering base image size

4. You wrote this Dockerfile to reduce image size but the final image is still large:

FROM python:3.12
RUN pip install flask
RUN rm -rf /root/.cache/pip

What is the main issue causing the large image?

medium

A. The pip cache is not cleaned because it is stored elsewhere

B. You should combine RUN commands to reduce layers

C. The base image python:3.12 is already large and cannot be reduced

D. Flask installation always creates large images regardless

Solution

1. Step 1: Understand Docker layers

   Each RUN creates a new layer; cleaning cache in a separate RUN keeps cache in previous layer.

2. Step 2: Combine commands to remove cache in same layer

   Combining pip install and cache removal in one RUN prevents cache from persisting in earlier layers.

3. Final Answer:

   You should combine RUN commands to reduce layers -> Option B

4. Quick Check:

   Combine RUN commands to clean caches in one layer [OK]

Hint: Combine install and cleanup in one RUN to reduce layers [OK]

Common Mistakes:

• Cleaning cache in separate RUN commands
• Assuming base image size can't be optimized
• Believing package size can't be reduced

5. You want to build a Docker image for a Go application but keep it as small as possible. Which multi-stage Dockerfile snippet achieves this best?

FROM golang:1.20 AS builder
WORKDIR /app
COPY . .
RUN go build -o myapp

FROM alpine:latest
COPY --from=builder /app/myapp /usr/local/bin/myapp
CMD ["myapp"]

hard

A. This build copies all source files to Alpine, increasing image size unnecessarily

B. Using Alpine as final image is bad because it lacks Go runtime

C. This multi-stage build compiles in golang image and copies only binary to Alpine, minimizing size

D. You should install Go in Alpine to build and run in one stage

Solution

1. Step 1: Understand multi-stage build purpose

   Build stage uses full Go image; final stage uses minimal Alpine with only binary copied.

2. Step 2: Analyze final image contents

   Only the compiled binary is copied, no source or build tools, keeping image small.

3. Final Answer:

   This multi-stage build compiles in golang image and copies only binary to Alpine, minimizing size -> Option C

4. Quick Check:

   Multi-stage build + minimal final image = small size [OK]

Hint: Use multi-stage builds to copy only final artifacts [OK]

Common Mistakes:

• Copying source files to final image
• Installing build tools in final image
• Building and running in same large image