Detached Mode

Look, if you've ever dealt with this in production, you know exactly what the problem is. When you run a web server like Nginx normally, it locks up your terminal window. You see the logs printing, but you cannot type any new commands until you hit Ctrl+C, which kills the server. In Docker, we solve this using 'Detached Mode'. By adding the -d flag to your run command (docker run -d nginx), the Docker Daemon starts the container completely in the background. It gives you your terminal prompt back instantly while the server runs silently. This isn't just academic theory—understanding the *why* behind this is what separates junior devs from senior engineers. When you deploy to a cluster, this is the mechanic that prevents catastrophic failure.

Look, if you've ever dealt with this in production, you know exactly what the problem is. If a container is running silently in the background, how do you know it exists? You use the docker ps command (Process Status). This is your radar. It lists every single active container currently running on your machine. It shows you the unique Container ID, the image it was built from, its uptime, and the ports it is using. If a container crashes, it immediately disappears from this active list. This isn't just academic theory—understanding the *why* behind this is what separates junior devs from senior engineers. When you deploy to a cluster, this is the mechanic that prevents catastrophic failure.

Look, if you've ever dealt with this in production, you know exactly what the problem is. When you are finished testing your background server, you must stop it to free up your computer's RAM and CPU. You do this using the docker stop command, followed by the Container ID (which you found using docker ps). This sends a graceful shutdown signal to the main process inside the container, giving it a few seconds to finish any active network requests before powering off. This isn't just academic theory—understanding the *why* behind this is what separates junior devs from senior engineers. When you deploy to a cluster, this is the mechanic that prevents catastrophic failure.

Detached Mode. When you run a web server like Nginx normally, it locks up your terminal window. You see the logs printing, but you cannot type any new commands until you hit Ctrl+C, which kills the server. In Docker, we solve this using 'Detached Mode'. By adding the -d flag to your run command (docker run -d nginx), the Docker Daemon starts the container completely in the background. It gives you your terminal prompt back instantly while the server runs silently.

Checking the Radar. If a container is running silently in the background, how do you know it exists? You use the docker ps command (Process Status). This is your radar. It lists every single active container currently running on your machine. It shows you the unique Container ID, the image it was built from, its uptime, and the ports it is using. If a container crashes, it immediately disappears from this active list.

You run a web server in the background using the -d flag. Which command must you type to see a list of all currently active, running containers?

• →docker ps
• →docker list

Stopping the Engine. When you are finished testing your background server, you must stop it to free up your computer's RAM and CPU. You do this using the docker stop command, followed by the Container ID (which you found using docker ps). This sends a graceful shutdown signal to the main process inside the container, giving it a few seconds to finish any active network requests before powering off.

Cleaning Up the Garbage. Here is a critical Docker secret: when you 'stop' a container, it is NOT deleted. It is simply powered off, exactly like turning off a laptop. It no longer consumes RAM, but it still consumes hard drive space. If you start and stop 100 containers over a month, your hard drive will fill up with 'dead' containers. To permanently delete a stopped container from your hard drive, you must use the docker rm command.

You run docker stop 1234abcd to stop a database container. Later that day, your hard drive is completely full. Why did stopping the container not free up any hard drive space?

• →Because docker stop only powers off the container (freeing RAM). The container still exists on the hard drive until you permanently delete it with docker rm.
• →Because Docker has a bug.

Batch 1 Mastered. Congratulations. You have completed the first major phase of your Docker Masterclass. You understand why containers exist, how the Engine's architecture separates the client and server, where Images are stored, and how to command the lifecycle of a container from execution to deletion. You are now ready to write your own custom blueprints.