Essential Docker CLI

Introduction

Master a dozen commands and you can do 95% of daily Docker work. Group them by what they manage: images, containers, volumes, networks.

Purpose of this lesson

This lesson teaches Essential Docker CLI as an engineering decision: what problem it solves, when to use it, how to implement it safely, and what signals tell you it is failing.

Understanding the topic

Use this as foundation knowledge before moving into image builds, Compose stacks, CI/CD, and production hardening. The goal is to understand the runtime model rather than memorize commands.

Core concepts to understand:

• Images: pull, images, rmi, build, tag, push.
• Containers: run, ps, start, stop, rm, exec, logs.
• Volumes/Networks: volume ls, network ls, inspect.
• System: system df, system prune, info, version.

Visual explanation

Architecture or command flow to keep in mind:

docker pull nginx:alpine       # download image
docker images                  # list local images
docker run -d --name web nginx:alpine
docker ps                      # running containers
docker logs -f web             # follow logs
docker exec -it web sh         # shell inside container
docker stop web && docker rm web
docker system prune -af        # reclaim disk (careful!)

Step-by-step explanation

1. Run the command or manifest exactly once on a clean Docker host and read the output carefully.
2. Inspect the object Docker created: image, container, network, volume, port mapping, process, or registry tag.
3. Break one realistic assumption such as a missing port, bad tag, stopped daemon, wrong network, or deleted volume.
4. Use docker ps, logs, inspect, stats, and system df to locate the failure.
5. Write the final command or configuration into a repeatable script, Compose file, or CI job.

Informative example

Use the example below as a working baseline, then verify the runtime behavior instead of assuming the command or file is correct.

docker pull nginx:alpine       # download image
docker images                  # list local images
docker run -d --name web nginx:alpine
docker ps                      # running containers
docker logs -f web             # follow logs
docker exec -it web sh         # shell inside container
docker stop web && docker rm web
docker system prune -af        # reclaim disk (careful!)

A production-minded check usually includes docker ps, docker logs, docker inspect, and one validation from outside the container such as curl, a database connection, or a registry pull.

# Verification loop for Essential Docker CLI
docker ps -a
docker logs --tail=100 <container-name>
docker inspect <container-or-image-name>
docker system df

Real-world use

Even seasoned engineers keep a cheat sheet of these commands open in a second window. Aliases like alias d=docker save thousands of keystrokes per week.

Enterprise use cases

In a mature engineering organization, Essential Docker CLI is documented as a repeatable pattern with approved base images, ownership labels, CI checks, security expectations, rollback notes, and troubleshooting commands. The difference between a tutorial and production practice is that every container decision must be observable, reviewable, and reversible.

Best practices

• Use --name on every long-running container — easier to manage than random IDs.
• Get comfortable with docker inspect — it answers 80% of 'why is it doing that?' questions.

Common mistakes

• docker system prune -af --volumes deletes everything, including volumes — read twice.

Debugging tips

• Read logs before restarting; a restart often removes the timing context you need for root cause analysis.
• Use docker inspect to compare configured state with actual runtime state.
• Check daemon health, disk usage, image tags, exit code, and port mappings before blaming application code.

Optimization strategies

• Prefer explicit names, labels, tags, and networks so cleanup and debugging stay predictable.
• Pin versions for repeatability, then update intentionally through a scheduled base-image refresh.
• Use docker system df and targeted prune commands to control local and CI disk growth.

Advanced interview questions

Hands-on exercise

Create a small lab for Essential Docker CLI: run the example, inspect the created Docker object, intentionally introduce one mistake, and record the command that reveals the failure. The goal is not just to make the happy path work; it is to build operational reflexes.

# Hands-on lab scaffold
mkdir -p docker-essential-docker-cli-lab
cd docker-essential-docker-cli-lab

# Add the Dockerfile, compose.yml, or command from this lesson.
# Then run one happy-path test and one broken-path test.
docker version
docker info
docker system df

Summary

Essential Docker CLI matters because Docker is not only a packaging tool; it is a runtime, build, networking, storage, and delivery workflow. Treat each lesson as a production habit: make it repeatable, inspectable, secure, and easy to debug.