Docker Container State Filtering: Complete Guide to Listing Only Stopped Containers

Overview of Docker Container State Management

In modern containerized deployment environments, effectively monitoring and managing container states is a critical aspect of operations. Docker provides powerful command-line tools for querying container information, with the docker ps command being the most commonly used tool for viewing container lists. By default, this command only displays running containers, while adding the -a parameter allows viewing all container instances, including stopped ones.

Detailed Explanation of State Filtering Mechanism

Docker's filtering system is based on a key-value pair model, allowing users to筛选 container lists according to specific criteria. For state filtering, the core parameter is status, which supports multiple predefined values to match different container lifecycle stages.

To specifically list stopped containers, the following command format can be used:

docker ps --filter "status=exited"

Or using the shorthand form:

docker ps -f "status=exited"

Here, the exited status value specifically refers to container instances that have completed execution and exited. From a technical implementation perspective, when a container's main process terminates, Docker automatically marks its state as exited, while retaining the container's filesystem layers and metadata information for subsequent log analysis or restart operations.

Classification and Comparison of Status Values

In addition to the exited status, Docker defines several other important status types:

• running: Currently executing active containers
• created: Container instances that have been created but not yet started
• paused: Running containers that have been manually paused
• restarting: Containers in the process of restarting

By combining different state filtering conditions, more precise container management can be achieved. For example, to view both stopped and created containers simultaneously, use:

docker ps -f "status=exited" -f "status=created"

Analysis of Practical Application Scenarios

In production environments, regularly cleaning up stopped containers is an important measure for maintaining system health. Through state filtering, administrators can quickly identify container resources that need cleanup:

# View all stopped containers
stopped_containers=$(docker ps -f "status=exited" -q)

# Batch delete stopped containers
if [ -n "$stopped_containers" ]; then
    docker rm $stopped_containers
fi

Such automated cleanup scripts can effectively release disk space and prevent the accumulation of stale container data. Simultaneously, state filtering facilitates troubleshooting; when a service abnormally terminates, relevant stopped containers can be quickly located and their log information examined.

Advanced Filtering Techniques

State filtering can be combined with other filter conditions to achieve multi-dimensional container queries. For example, combining name filtering with state filtering:

# Find stopped containers with specific names
docker ps -f "name=web-server" -f "status=exited"

Or combining time filtering to find containers stopped within a specific time frame:

# Find containers stopped within the last 24 hours
docker ps -f "status=exited" --since 24h

Best Practice Recommendations

Based on practical operational experience, we recommend the following best practices:

1. Always use explicit filter conditions in automated scripts to avoid relying on default behaviors
2. Regularly use state filtering to monitor container health and establish alert mechanisms
3. Combine with the --format parameter to customize output formats for improved readability
4. Integrate state checks into CI/CD pipelines to ensure deployment quality

By deeply understanding and skillfully applying Docker's state filtering functionality, developers and operations personnel can significantly enhance the management efficiency of containerized applications, building more stable and reliable cloud-native infrastructure.