Key Docker Concepts

Key Docker Concepts

Understanding these core concepts is essential for working with Docker:

Image

Think of a Docker image like a recipe card. It contains every ingredient and instruction needed to run your application like, the code, the tools, the settings, and all packaged into one file you can share with anyone.

When someone else uses your image, they get an exact copy of your environment. That means your app runs the same way on their laptop, your server, or a cloud provider. No more "it works on my machine" problems.

A Docker image bundles together:

• Your application's source code
• The language runtime it needs (Node.js, Python, Java, etc.)
• System libraries and dependencies
• Environment variables and configuration

Docker images are built from a file called a Dockerfile, a simple text file with step-by-step build instructions. Once built, images can be pushed to a Docker registry like Docker Hub so other people can download and use them.

Container

A Docker container is a live, running instance of a Docker image. If the image is a recipe, the container is the dish you cook from it.

When you run an image, Docker creates a container, which means, an isolated process that has its own filesystem, its own network, and everything it needs to run your app. Docker containers are:

• Isolated from other containers and the host system
• Lightweight and portable
• Run processes with their own filesystem
• Ephermal

Dockerfile

A Dockerfile is a plain text file that contains a series of instructions telling Docker how to build a Docker image. Docker reads the file from top to bottom and executes each step in order.

Think of it like a script: "Start with this base, install these tools, copy these files, then run this command."

Here's a basic Dockerfile for a Node.js application:

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

Registry

A Docker registry is a storage and distribution system for Docker images, like GitHub, but for images instead of code. Once you've built a Docker image, you need somewhere to store it and share it. That's exactly what a Docker registry is for.

You push images to a registry to share them, and pull images from a registry to use them. This makes it easy to distribute your application to teammates, CI/CD pipelines, or production servers.

What Is Docker Hub?

Docker Hub is the default public registry and the largest one in the world. It hosts millions of official and community images for popular software like Postgres, Nginx, Redis, and Node.js. When you run a command like docker pull node:18, Docker automatically fetches that image from Docker Hub.

Docker Compose

Real-world applications rarely run as a single service. A typical web app might have a frontend, a backend API, a database, and a cache. Docker Compose is the tool that ties them all together. Docker Compose is a tool for defining and running multi-container Docker applications. Instead of starting each container with a separate docker run command, you describe all your services in a single file and launch everything at once.