Running Docker Containers from Docker Hub

1. The Docker Ecosystem: Key Components

Before we type our first command, it's essential to understand the main parts of the Docker platform that work together.

• Docker Engine: This is the core of Docker. It's a background service (also called a daemon) that runs on your host machine. It's responsible for building, running, and managing your containers.
• Docker Client (CLI): This is the command-line tool you'll use to interact with the Docker Engine. When you type a command like docker run, the client sends instructions to the daemon.
• Docker Image: An image is a read-only template containing everything needed to run an application: the code, a runtime, libraries, environment variables, and configuration files. You can think of it as a blueprint or a recipe.
• Docker Container: A container is a runnable, live instance of an image. If an image is the blueprint, a container is the actual house built from it. You can create, start, stop, move, and delete containers.
• Docker Hub: A cloud-based registry service where you can find and share container images. It's the default public registry that Docker uses, hosting thousands of official and community-built images. Think of it as GitHub, but for Docker images.

The diagram below provides a great high-level overview of how these pieces fit together.

2. Installing Docker

The first practical step is to install the Docker Engine on your machine. The process varies slightly depending on your operating system. For most development work on a personal computer, you will install Docker Desktop, which bundles the Docker Engine, the client CLI, and a helpful graphical user interface. On a Linux server, you would typically install Docker Engine directly.

Important Note for Linux Users:
By default, Docker commands require root privileges. To run docker commands without sudo every time, you should add your user to the docker group. This is a standard post-installation step. You can do this with the following command:

sudo usermod -aG docker ${USER}

After running this command, you will need to log out and log back in for the group membership to be reapplied.

3. Running Your First Containers

With Docker installed, you're ready for the most satisfying part: running a container. The docker run command is your primary tool for this. It tells the Docker Engine to create and start a container from a specified image. If the image doesn't exist on your machine, Docker will automatically download (or "pull") it from Docker Hub.

The Classic: hello-world

The hello-world image is a tiny container designed specifically to test that your Docker installation is working correctly.

In your terminal, run the following command:

docker run hello-world

You should see output similar to this:

Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
...
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.
...

Let's break down what just happened:

1. The Docker client told the Docker Engine to run a container from the hello-world image.
2. The engine checked for a local image named hello-world. It didn't find one.
3. The engine then connected to Docker Hub and pulled the hello-world:latest image.
4. Once downloaded, the engine created a new container from that image.
5. The container executed its command, which printed the "Hello from Docker!" message to your terminal, and then it exited.

A Real-World Example: Nginx Web Server

Running "hello-world" is a great start, but let's run something more practical. Nginx is a very popular, high-performance web server. With Docker, you can have it up and running with a single command, without installing anything directly on your host OS.

The command you ran was likely:
docker run -d -p 8080:80 nginx

Let's dissect this command:

• docker run: The command to create and start a container.
• -d: This stands for detached mode. It runs the container in the background and prints the container ID. Without this, your terminal would be attached to the container's logs.
• -p 8080:80: This is for port mapping. It maps port 8080 on your host machine to port 80 inside the container. Nginx listens on port 80 by default, so this mapping makes it accessible from your host's browser via localhost:8080.
• nginx: The name of the image to use from Docker Hub.

By running this one line, you've downloaded and launched a fully functional web server in an isolated environment. This is the core value proposition of Docker for a DevOps workflow: fast, reproducible, and portable application deployment.

4. Finding Images on Docker Hub

How did we know to use hello-world or nginx? These are official images available on Docker Hub. You can search for images directly from the command line or by browsing the Docker Hub website.

For example, to search for images related to the Redis in-memory database, you could run:

docker search redis

This will return a list of public images, with official images usually listed at the top and marked as [OK] under the OFFICIAL column. Using official images is highly recommended for security and stability.

Conclusion

Congratulations! You have successfully moved from theory to practice by installing Docker and running your first containers. This is a fundamental skill for any DevOps engineer and the first major step in mastering containerization.

Key Takeaways:

• The Docker ecosystem consists of the Docker Engine (daemon), a client (CLI), images (blueprints), and containers (running instances).
• Docker Hub is the central public registry for finding and sharing images.
• The docker run command is used to create and start containers. It automatically pulls images from Docker Hub if they are not present locally.
• Command-line flags like -d (detached) and -p (port mapping) are crucial for running services like web servers.

Next Up: Managing Container Lifecycle

You've now created a running Nginx container. In the next lesson, "Manage container lifecycle using docker run, stop, start, and rm commands," we will explore how to manage this container. You will learn how to view its status, stop it, restart it, and clean it up once you're finished.