Why RUN instruction for executing commands in Docker? - Purpose & Use Cases

The Big Idea

What if you never had to type the same setup commands again and could share your environment with a single file?

The Scenario

Imagine you want to set up a software environment by installing packages and configuring settings manually on your computer every time you start a project.

You open a terminal, type commands one by one, and hope you don't miss any step.

The Problem

This manual way is slow and easy to forget steps.

Each time you start fresh, you repeat the same commands, wasting time and risking mistakes.

It's like writing the same recipe over and over instead of having a ready-made meal.

The Solution

The RUN instruction in Docker lets you write all those commands once inside a file called a Dockerfile.

When you build your Docker image, it runs those commands automatically, creating a ready-to-use environment every time.

Before vs After

✗ Before

apt-get update
apt-get install -y curl
mkdir /app
cd /app

✓ After

RUN apt-get update && apt-get install -y curl && mkdir /app && cd /app

What It Enables

You can create consistent, repeatable environments quickly without typing commands manually each time.

Real Life Example

A developer shares a Dockerfile with teammates so everyone runs the same setup commands automatically, avoiding setup errors and saving hours.

Key Takeaways

Manual command execution is slow and error-prone.

RUN instruction automates command execution inside Docker images.

This creates fast, repeatable, and consistent environments.

Practice

1. What does the RUN instruction do in a Dockerfile?

easy

A. Executes commands during the image build process

B. Starts a container from an image

C. Copies files from host to container

D. Defines environment variables for the container

Solution

1. Step 1: Understand Dockerfile instructions

   The RUN instruction is used to execute commands while building the Docker image.

2. Step 2: Differentiate from other instructions

   Other instructions like COPY or ENV serve different purposes, not command execution.

3. Final Answer:

   Executes commands during the image build process -> Option A

4. Quick Check:

   RUN = execute commands during build [OK]

Hint: RUN runs commands while building the image [OK]

Common Mistakes:

• Confusing RUN with CMD or ENTRYPOINT
• Thinking RUN starts containers
• Mixing RUN with COPY or ENV

2. Which of the following is the correct syntax to install curl using RUN in a Debian-based Docker image?

easy

A. RUN apt-get install curl

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

C. RUN install curl

D. RUN curl install

Solution

1. Step 1: Understand package installation in Debian

   Before installing packages, you must update the package list using apt-get update.

2. Step 2: Use correct flags and chaining

   The -y flag auto-confirms installation, and chaining commands with && ensures update runs before install.

3. Final Answer:

   RUN apt-get update && apt-get install -y curl -> Option B

4. Quick Check:

   Update then install with -y flag [OK]

Hint: Always update before install and use -y flag [OK]

Common Mistakes:

• Skipping apt-get update
• Not using -y to auto-confirm
• Wrong command order or syntax

3. Given this Dockerfile snippet:

FROM ubuntu:latest
RUN echo "Hello" && echo "World"

What will be the output when building this Docker image?

medium

A. Hello World printed during build

B. No output shown during build

C. Error because of missing semicolon

D. Only 'Hello' printed, 'World' ignored

Solution

1. Step 1: Analyze the RUN command chaining

   The command uses && to run two echo commands sequentially during build.

2. Step 2: Understand Docker build output

   During build, the output of RUN commands is shown in the terminal, so both 'Hello' and 'World' will print.

3. Final Answer:

   Hello World printed during build -> Option A

4. Quick Check:

   RUN shows command output during build [OK]

Hint: RUN output appears during build, && runs commands sequentially [OK]

Common Mistakes:

• Thinking RUN output is hidden
• Confusing && with ;
• Assuming only first command runs

4. Identify the error in this Dockerfile RUN instruction:

RUN apt-get update & apt-get install -y git

medium

A. RUN cannot have multiple commands

B. Missing -y flag for apt-get install

C. apt-get update should be last command

D. Using single & instead of && causes syntax error

Solution

1. Step 1: Check command chaining syntax

   Single & runs command in background and is invalid in Docker RUN; && is needed to chain commands properly.

2. Step 2: Confirm correct chaining for sequential execution

   Using && ensures the second command runs only if the first succeeds.

3. Final Answer:

   Using single & instead of && causes syntax error -> Option D

4. Quick Check:

   Use && to chain commands in RUN [OK]

Hint: Use && not & to chain commands in RUN [OK]

Common Mistakes:

• Using & instead of &&
• Ignoring command chaining rules
• Assuming RUN runs commands in parallel

5. You want to reduce Docker image layers by combining multiple commands in a single RUN instruction. Which is the best way to do this?

hard

A. Use multiple RUN instructions, one per command

B. Separate commands with semicolons in multiple RUN lines

C. Chain commands with && inside one RUN instruction

D. Use CMD instead of RUN for multiple commands

Solution

1. Step 1: Understand Docker image layers

   Each RUN instruction creates a new image layer, increasing image size.

2. Step 2: Combine commands to reduce layers

   Chaining commands with && inside one RUN instruction runs them sequentially in a single layer.

3. Final Answer:

   Chain commands with && inside one RUN instruction -> Option C

4. Quick Check:

   Combine commands with && to reduce layers [OK]

Hint: Chain commands with && in one RUN to reduce layers [OK]

Common Mistakes:

• Using multiple RUNs increases layers
• Using CMD instead of RUN for build steps
• Separating commands with semicolons without chaining