Why orchestration matters in Docker - Why It Works

Introduction

When you run many containers for your app, managing them one by one becomes confusing and slow. Orchestration helps by automatically starting, stopping, and organizing containers so everything works smoothly together.

When you want to run multiple containers that depend on each other, like a web server and a database.

When your app needs to keep running even if one container crashes.

When you want to update your app without stopping all containers at once.

When you need to balance traffic between many copies of the same container.

When you want to easily add or remove containers based on how busy your app is.

Commands

Create a network so containers can talk to each other easily and securely.

Terminal

docker network create my-app-network

Expected Output

6f8c1e2a3b4c5d6e7f8a9b0c1d2e3f4g5h6i7j8k9l0m1n2o3p4q5r6s7t8u9v0w1x2y3z4

Start a database container connected to the network so other containers can use it.

Terminal

docker run -d --name my-db --network my-app-network postgres:15

Expected Output

e3f1a2b3c4d5e6f7g8h9i0j1k2l3m4n5o6p7q8r9s0t1u2v3w4x5y6z7a8b9c0d1

→

-d - Run container in background

→

--name - Assign a name to the container

→

--network - Connect container to a specific network

Start a web server container on the same network and expose it on port 8080 of your computer.

Terminal

docker run -d --name my-web --network my-app-network -p 8080:80 nginx:1.25

Expected Output

f1e2d3c4b5a697887766554433221100ffeeddccbbaa99887766554433221100

→

-p - Map container port to host port

→

-d - Run container in background

→

--network - Connect container to a specific network

Check that both containers are running and see their details.

Terminal

docker ps

Expected Output

CONTAINER ID   IMAGE         COMMAND                  CREATED          STATUS          PORTS                  NAMES

f1e2d3c4b5a6   nginx:1.25    "nginx -g 'daemon off;'"   10 seconds ago   Up 9 seconds    0.0.0.0:8080->80/tcp   my-web

e3f1a2b3c4d5   postgres:15   "docker-entrypoint.s…"   15 seconds ago   Up 14 seconds                          my-db

Key Concept

Orchestration automates managing many containers so they work together reliably without manual effort.

Common Mistakes

Running containers without connecting them to the same network.

Containers cannot communicate, so your app parts won't work together.

Create a user-defined network and connect all related containers to it.

Exposing container ports without mapping them to host ports.

You cannot access the container services from outside the host machine.

Use the -p flag to map container ports to host ports.

Starting containers manually one by one every time.

It is slow, error-prone, and hard to keep track of all containers.

Use orchestration tools or scripts to automate container management.

Summary

Create a network so containers can communicate securely.

Start containers connected to the network with proper port mapping.

Use commands like docker ps to verify containers are running.

Orchestration saves time and prevents errors when managing many containers.