Installing Docker and Running Your First Container

Before you can work with containers you need Docker installed and a feel for running containers from the command line. Docker is distributed as Docker Desktop (the easy, GUI-inclusive option for macOS, Windows, and Linux) or Docker Engine (the CLI-only daemon for Linux servers). Once installed, a single command pulls an image and runs your first container, exercising the whole pipeline.

Running a container is the core daily action, controlled by docker run with a handful of essential flags: detached mode to run in the background, port publishing to reach a container's service, naming for easy reference, interactive mode for a shell, and automatic cleanup. Learning these flags well makes everything that follows fluent.

This lesson covers installing Docker, verifying it works, running your first container, and the most important docker run flags. It is deliberately hands-on: by the end you should be able to pull an image from Docker Hub and run a real service, like a web server, reachable from your browser.

Analogy🏏Cricket

🏏 Think of it like cricket: Just as before a player can take the field they must have their kit ready and know the basic commands — how to take guard, call for a run, signal the umpire, before working with containers you install Docker and learn the basic run commands. The insight is that fluency in the fundamentals comes before anything advanced: the player masters the basic calls before complex tactics, exactly as you master docker run and its key flags before building images or orchestrating services.