Docker & Kubernetes for Developers · Lesson

Crafting Dockerfiles for Images

Learn to write Dockerfiles to define how your application environment and dependencies are packaged into an image.

Crafting Dockerfiles for Images is a free Docker & Kubernetes for Developers lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Docker & Kubernetes for Developers learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

What are Dockerfiles?

Welcome to creating your own Docker images! The heart of this process is the Dockerfile.

A Dockerfile is a simple text file that contains a series of instructions. These instructions tell Docker exactly how to build a Docker image, step by step.

Why Use a Dockerfile?

Dockerfiles automate the image creation process. Instead of manually setting up an environment, you define it once in a Dockerfile.

Reproducibility: Ensures everyone builds the exact same image.
Version Control: Dockerfiles can be stored in Git, just like your code.
Efficiency: Speeds up development and deployment workflows.

Starting Point: The FROM Instruction

Every Dockerfile must start with the FROM instruction. It specifies the base image your image will be built upon.

Think of it as choosing the operating system and initial software for your container. For example, ubuntu:22.04 or node:18-alpine.

FROM node:18-alpine

Running Commands: The RUN Instruction

The RUN instruction executes commands during the image build process. This is where you install software, update packages, or create directories.

Each RUN instruction creates a new layer in your image.

FROM node:18-alpine
RUN apk add --no-cache git

Setting the Workspace: WORKDIR

The WORKDIR instruction sets the working directory for any subsequent RUN, CMD, ENTRYPOINT, COPY, or ADD instructions.

It's good practice to set a specific directory for your application files.

FROM node:18-alpine
WORKDIR /app

Adding Files: The COPY Instruction

The COPY instruction copies files or directories from your local machine (the build context) into the Docker image filesystem.

The first argument is the source path on your machine, the second is the destination path inside the image.

FROM node:18-alpine
WORKDIR /app
COPY package*.json ./

Installing Dependencies

After copying your project's dependency files (like package.json for Node.js), you'll typically use RUN again to install them.

This step ensures your application has all it needs to run.

FROM node:18-alpine
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .

Exposing Ports: The EXPOSE Instruction

The EXPOSE instruction informs Docker that the container listens on the specified network ports at runtime.

It's documentation for users, not an actual publishing of the port. You'll publish ports when you run the container.

FROM node:18-alpine
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 3000

Default Command: The CMD Instruction

The CMD instruction provides a default command to be executed when a container starts from the image.

Unlike RUN, CMD runs when the container is launched, not during the build. You can override it when running the container.

FROM node:18-alpine
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 3000
CMD ["npm", "start"]

Complete Dockerfile Example

Here's a full example of a simple Dockerfile for a Node.js web application. Each line contributes to building the final image.

# Use an official Node.js runtime as a parent image
FROM node:18-alpine

# Set the working directory in the container
WORKDIR /app

# Copy package.json and package-lock.json to install dependencies
COPY package*.json ./

# Install application dependencies
RUN npm install

# Copy the rest of the application code
COPY . .

# Make port 3000 available to the world outside this container
EXPOSE 3000

# Define the command to run your app
CMD ["npm", "start"]

Dockerfile Instruction Check

Which Dockerfile instruction is used to execute commands during the image build process, such as installing packages or creating directories?

Recap: Crafting Dockerfiles

You've learned the essential instructions for crafting Dockerfiles:

FROM: Sets the base image.
RUN: Executes commands during build.
WORKDIR: Sets the working directory.
COPY: Copies files into the image.
EXPOSE: Declares listening ports.
CMD: Sets the default command to run on container start.

Mastering these allows you to define your application's environment precisely!

Frequently asked questions

Is the “Crafting Dockerfiles for Images” lesson free?

Yes — the full text of “Crafting Dockerfiles for Images” is free to read here on the web, and the Docker & Kubernetes for Developers course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Docker & Kubernetes for Developers course, upgrade to CoddyKit PRO.

What will I learn in “Crafting Dockerfiles for Images”?

Learn to write Dockerfiles to define how your application environment and dependencies are packaged into an image. You practise Docker & Kubernetes for Developers with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Docker & Kubernetes for Developers?

No prior experience is required. Docker & Kubernetes for Developers on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Crafting Dockerfiles for Images” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Docker & Kubernetes for Developers lesson?

Yes. Every Docker & Kubernetes for Developers lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Docker & Kubernetes for Developers