Docker: How to stop all containers

When you're taking your first steps in the world of Docker development, it's common to end up with multiple containers running simultaneously. Some are in testing, others are in local production, and still others were simply forgotten after a Docker run. At some point, you'll need to clean up your environment and stop all those containers. And this is where many people ask: How do I stop all Docker containers at once?

The good news is that Docker offers direct and efficient commands to perform this task without complications. You don't need a complex script or an additional tool: you just need to know the right instructions, and that's precisely what we're going to explain in this article.

Stopping all running containers: the key command

The most direct and recommended way to stop all currently running containers is this:

docker stop $(docker ps -q)

Let's break down what happens here:

• docker ps -q lists all the IDs of the running containers (the -q option stands for quiet, so it only returns the IDs).
• docker stop takes a list of IDs as an argument and stops them one by one.

This command is safe and effective. If there are no running containers, it won't do anything or generate errors. In development environments, it can save you several minutes of repetitive commands.

What if I also want to remove containers?

Often, stopping isn't enough. Many developers want to clean up their environment completely, including removing stopped containers. In that case, the next step is to use:

docker rm $(docker ps -a -q)

This command removes all containers, whether they are running or not (because docker ps -a lists them all). But be careful: you can't remove a running container. That's why it's important to stop them first with docker stop.

To do both in one line, you can chain commands:

docker stop $(docker ps -q) && docker rm $(docker ps -a -q)

This combo is widely used in staging and testing environments, where containers are ephemeral.

Why stop Docker containers?

Stopping containers has implications for both performance and security. Each active container consumes resources: CPU, memory, disk space (if it generates logs or cache). Additionally, the ports they expose could be interfering with other local services.

According to a study published by Datadog in 2023, more than 70% of developers who regularly use Docker have at least three containers running simultaneously on their local machine, even when they are not using them. This creates bottlenecks that affect both system performance and the stability of test environments.

What about containers in production?

In production environments, stopping all containers is generally not a good practice unless it's part of a controlled restart strategy (as part of a CI/CD pipeline or a major update). In those cases, tools like Docker Compose or Kubernetes are often used to manage services more robustly.

If you're using docker-compose, you can stop all services defined in your docker-compose.yml file with:

docker-compose down

This command stops and removes all containers, networks, and volumes defined by the file. Ideal for shutting down an entire project in an orderly manner.

Automate: Create Your Own Alias

If you find yourself stopping containers frequently, you can add an alias to your ~/.bashrc or ~/.zshrc file:

alias docker-stop-all="docker stop \$(docker ps -q)"

After reloading the terminal, simply run docker-stop-all to stop everything in one fell swoop.

Best Practices: When to Stop and When to Delete

As a software development agency, we recommend following these guidelines:

• In development: Stop containers when you're done for the day, especially if you're working with resource-intensive services like databases, file servers, or proxies.
• In testing: Delete containers when you no longer need them. This keeps your environment clean and prevents network or port conflicts.
• In production: Use orchestration tools and avoid manual cleanup unless you're performing planned maintenance.

Conclusion: Full Control Over Your Docker Environment

Knowing how to stop all Docker containers is not only a useful skill, but essential for any developer who wants to keep their environment under control. This small command can make a huge difference in the stability, performance, and organization of your local environment.

At Rootstack, we help development teams deploy optimized, automated, and scalable Docker environments. Whether you're just getting started with Docker or want to take your architecture to the next level, our team can help with custom configurations, automation with Docker Compose, CI/CD integration, and cloud deployment.

We recommend you on video