Squashing layers in Docker - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does 'squashing layers' mean in Docker?

Squashing layers means combining multiple image layers into one to reduce image size and improve efficiency.

beginner

Why is squashing layers useful in Docker images?

It reduces the final image size, speeds up downloads, and makes the image easier to manage.

intermediate

Which Docker command option allows squashing layers during build?

The option is --squash used with docker build to combine layers.

intermediate

Does squashing layers affect Docker cache usage?

Yes, squashing can reduce cache efficiency because it merges layers, making incremental builds less effective.

intermediate

How can you enable squashing layers in Docker BuildKit?

Set the environment variable DOCKER_BUILDKIT=1 and use --squash with docker build.

What is the main benefit of squashing layers in Docker images?

A Smaller image size

B Faster container startup

C More layers created

D Improved network speed

Squashing layers reduces the image size by combining multiple layers into one.

Which Docker build option enables layer squashing?

A --flatten

B --compress

C --squash

D --merge

The --squash option is used to squash layers during a Docker build.

What is a downside of squashing layers in Docker builds?

A Reduced cache efficiency

B Slower build times

C Increased image size

D More complex Dockerfiles

Squashing reduces cache efficiency because it merges layers, making incremental builds less effective.

To use squashing with Docker BuildKit, what must you do?

A Use --compress flag only

B Set DOCKER_BUILDKIT=1 and use --squash

C Enable experimental Docker mode

D No special setup needed

You must enable BuildKit with DOCKER_BUILDKIT=1 and add --squash to the build command.

Which of these is NOT true about squashing layers?

A It merges multiple layers into one

B It may reduce build cache effectiveness

C It can reduce image size

D It always speeds up container startup

Squashing layers reduces image size but does not necessarily speed up container startup.

Explain what squashing layers means in Docker and why it might be useful.

Think about how combining layers affects image size and build process.

Describe how to enable squashing layers when building a Docker image using BuildKit.

Remember the environment variable and the build command option.

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