Squashing layers in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why squash Docker image layers?

What is the main benefit of squashing layers in a Docker image?

A It automatically updates the base image to the latest version.

B It increases build speed by caching all layers separately.

C It reduces the final image size by combining multiple layers into one.

D It splits the image into multiple smaller images for easier distribution.

💡 Hint

Think about how layers add up in size and how combining them affects the image.

Squashing merges multiple layers into a single one, which reduces the overall image size and can improve deployment efficiency.

💻 Command Output

intermediate

Output of Docker build with --squash

What output will you see when running docker build --squash -t myapp . if the Docker daemon supports squashing?

A Successfully built <image_id> with all layers squashed into one.

B Error: unknown flag: --squash

C Warning: --squash ignored, using default layering.

D Build completed but layers remain separate.

💡 Hint

Consider if the Docker daemon supports the experimental feature for squashing.

If the daemon supports squashing, the build output confirms success and shows the image ID with layers combined.

❓ Configuration

advanced

Enable Docker experimental features for squashing

Which configuration change enables Docker's experimental features to allow layer squashing?

A Run Docker with --enable-experimental flag every time.

B Set environment variable DOCKER_SQUASH=enabled before building.

C Install a separate Docker plugin for squashing layers.

D Add "experimental": true to the daemon.json file and restart Docker.

💡 Hint

Think about Docker daemon configuration files and how to enable experimental features globally.

Adding "experimental": true in /etc/docker/daemon.json enables experimental features like --squash, requiring a Docker restart.

❓ Troubleshoot

advanced

Why does --squash flag cause an error?

You run docker build --squash -t myapp . but get the error: "unknown flag: --squash". What is the most likely cause?

A Docker daemon experimental features are not enabled.

B The Dockerfile syntax is incorrect.

C The build context directory is missing.

D The Docker client version is too new for this flag.

💡 Hint

Check if the Docker daemon supports the feature you are trying to use.

The --squash flag requires experimental features enabled on the Docker daemon; otherwise, it is unknown and causes an error.

🔀 Workflow

expert

Best workflow to minimize image size with squashing

Which workflow best minimizes Docker image size using squashing while keeping build cache benefits?

A Squash all layers in every build to one layer immediately.

B Use multi-stage builds and squash only the final stage layers.

C Build without squashing, then manually delete intermediate images.

D Use a single RUN command for all steps without squashing.

💡 Hint

Consider how multi-stage builds and squashing can work together to optimize size and caching.

Multi-stage builds allow separating build and runtime stages; squashing only the final stage reduces size without losing cache benefits from earlier stages.

Practice

1. What is the main purpose of docker build --squash?

easy

A. To speed up the build process by skipping some steps

B. To create multiple images from one Dockerfile

C. To combine multiple image layers into a single layer to reduce image size

D. To automatically update the base image to the latest version

Solution

1. Step 1: Understand what layers are in Docker images

   Docker images are made of layers created by each command in the Dockerfile.

2. Step 2: Purpose of squashing layers

   Squashing merges these layers into one to reduce the final image size and improve efficiency.

3. Final Answer:

   To combine multiple image layers into a single layer to reduce image size -> Option C

4. Quick Check:

   Squashing = combining layers [OK]

Hint: Squash means merge layers to save space [OK]

Common Mistakes:

• Thinking it speeds up build time
• Confusing squashing with creating multiple images
• Assuming it updates base images automatically

2. Which of the following is the correct syntax to build a Docker image with squashed layers?

easy

A. docker build -squash=true -t myimage .

B. docker build -squash -t myimage .

C. docker build --squash=true -t myimage .

D. docker build --squash -t myimage .

Solution

1. Step 1: Check the correct flag format for squashing

   The correct flag is --squash without an equals sign or single dash.

2. Step 2: Validate the full command syntax

   The command docker build --squash -t myimage . correctly uses the flag and tags the image.

3. Final Answer:

   docker build --squash -t myimage . -> Option D

4. Quick Check:

   Correct flag is double dash --squash [OK]

Hint: Use double dash --squash without equals sign [OK]

Common Mistakes:

• Using single dash -squash
• Adding =true after --squash
• Misplacing the flag after the context dot

3. Given this Dockerfile:

FROM alpine
RUN echo 'Hello' > /file1
RUN echo 'World' > /file2

What is the main difference in the image size when built with and without --squash?

medium

A. The image with --squash is smaller because layers are combined

B. The image with --squash is larger because it adds extra metadata

C. Both images have the same size because layers do not affect size

D. The image without --squash is smaller because layers are cached

Solution

1. Step 1: Understand how layers affect image size

   Each RUN command creates a new layer, adding to the total image size.

2. Step 2: Effect of --squash on layers

   Using --squash merges layers, removing intermediate data and reducing size.

3. Final Answer:

   The image with --squash is smaller because layers are combined -> Option A

4. Quick Check:

   Squash reduces size by merging layers [OK]

Hint: Squash merges layers, reducing image size [OK]

Common Mistakes:

• Thinking squashing adds metadata and increases size
• Believing layers do not affect image size
• Confusing caching with squashing effects

4. You run docker build --squash -t myapp . but get an error saying the flag is unknown. What is the most likely cause?

medium

A. The image tag is missing

B. Docker experimental features are not enabled

C. The Dockerfile has syntax errors

D. The build context path is incorrect

Solution

1. Step 1: Understand requirements for --squash flag

   The --squash flag requires Docker experimental features to be enabled.

2. Step 2: Identify cause of unknown flag error

   If experimental features are off, Docker does not recognize --squash and throws an error.

3. Final Answer:

   Docker experimental features are not enabled -> Option B

4. Quick Check:

   Enable experimental features to use --squash [OK]

Hint: Enable experimental features to use --squash [OK]

Common Mistakes:

• Assuming Dockerfile errors cause unknown flag
• Thinking missing tag causes flag error
• Blaming build context path for flag issues

5. You want to reduce your Docker image size by squashing layers but also keep some intermediate layers for caching. Which approach is best?

hard

A. Use multi-stage builds and squash only the final stage

B. Use --squash on every build to squash all layers

C. Avoid squashing and rely on layer caching only

D. Manually delete intermediate files after build

Solution

1. Step 1: Understand multi-stage builds

   Multi-stage builds allow creating intermediate images for caching and a final optimized image.

2. Step 2: Combine multi-stage builds with squashing

   Squashing only the final stage reduces image size while keeping intermediate layers for cache.

3. Final Answer:

   Use multi-stage builds and squash only the final stage -> Option A

4. Quick Check:

   Multi-stage + squash final stage = best size and cache [OK]

Hint: Squash final stage in multi-stage builds for best results [OK]

Common Mistakes:

• Squashing all layers loses caching benefits
• Avoiding squashing misses size reduction
• Deleting files manually is error-prone