Why WORKDIR instruction for directory in Docker? - Purpose & Use Cases

The Big Idea

What if you could stop repeating long folder paths and avoid silly mistakes in your Docker builds?

The Scenario

Imagine you are building a Docker image and need to run several commands inside a specific folder. Without setting a working directory, you must type the full path every time you want to access files or run commands there.

The Problem

This manual way is slow and error-prone because you have to repeat long paths in every command. It's easy to make typos or forget to change directories, causing build failures or unexpected results.

The Solution

The WORKDIR instruction sets a default directory inside the container. After setting it once, all following commands run inside that folder automatically, making your Dockerfile cleaner and less error-prone.

Before vs After

✗ Before

RUN mkdir -p /app && cd /app && touch file.txt
RUN cd /app && ls

✓ After

WORKDIR /app
RUN touch file.txt
RUN ls

What It Enables

It enables simpler, clearer Dockerfiles where commands naturally run in the right folder without repeating paths.

Real Life Example

When building a web app image, you can set WORKDIR to the app folder so all build steps like installing dependencies and copying files happen inside that folder automatically.

Key Takeaways

Manually changing directories in Dockerfiles is repetitive and error-prone.

WORKDIR sets a default folder for all following commands.

This makes Dockerfiles easier to read and maintain.