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.