How to fix Error response from daemon: container is paused in Docker

DockerBEGINNERLOWUpdated Dec 6, 2025· 222 views

The 'container is paused' error occurs when you try to perform operations on a Docker container that has been suspended using the pause command. Simply unpause the container with 'docker unpause' to resume normal operations.

Quick fix

Fixes Error response from daemon: container is paused

docker ps
  1. Check if the container is paused
  2. Unpause the container
  3. Unpause multiple containers at once
  4. Now perform your intended operation
docker — error
docker ps
Error response from daemon: container is paused

What this error means

This error occurs when you attempt to interact with a Docker container that is currently in a paused state. The full error message typically reads: "Error response from daemon: container is paused" or variations like "Container is paused, unpause the container before exec". When a container is paused, Docker uses the Linux cgroups freezer to suspend all processes inside the container. Unlike stopping a container (which sends SIGTERM/SIGKILL signals), pausing freezes processes in place - they remain in memory with all their state preserved, but receive no CPU time and cannot execute any instructions. This state is useful for temporarily suspending workloads without losing state, but it prevents most container operations including exec, stop, restart, and attach until the container is unpaused.

Typical symptoms

  • 'docker exec' fails with 'Container is paused, unpause the container before exec'
  • 'docker stop' fails with 'Cannot stop container: Container is paused'
  • 'docker restart' fails with 'Cannot restart container: Container is paused'
  • Container shows 'Up X minutes (Paused)' status in 'docker ps' output
  • Container processes are unresponsive but container appears to be running
  • Network connections to the container hang or timeout

Common causes

  1. Container was explicitly paused using 'docker pause' command
  2. Docker Compose service was paused using 'docker compose pause'
  3. Automated scripts or orchestration tools paused the container
  4. Docker Desktop was paused (which pauses all containers)
  5. System resource management tools paused containers to free resources

How to fix "Error response from daemon: container is paused"

1Check if the container is paused

First, verify that the container is actually in a paused state:

bash
docker ps

Look for your container in the output. A paused container will show a status like:

bash
CONTAINER ID   IMAGE     STATUS                  NAMES
abc123def456   nginx     Up 10 minutes (Paused)  my_container

You can also inspect the container directly:

bash
docker inspect <container_name_or_id> --format='{{.State.Paused}}'

If this returns true, the container is paused.

2Unpause the container

To resume a paused container, use the docker unpause command:

bash
docker unpause <container_name_or_id>

If successful, the command completes silently. Verify the container is running normally:

bash
docker ps

The status should now show "Up X minutes" without the "(Paused)" indicator.

3Unpause multiple containers at once

If you have multiple paused containers, you can unpause them all at once:

bash
# Unpause specific containers
docker unpause container1 container2 container3

# Unpause all paused containers
docker unpause $(docker ps -q --filter "status=paused")

For Docker Compose services:

bash
# Unpause all services in the compose project
docker compose unpause

# Unpause a specific service
docker compose unpause <service_name>
4Now perform your intended operation

After unpausing, you can perform the operation that previously failed:

bash
# Execute a command inside the container
docker exec -it <container_name_or_id> /bin/bash

# Stop the container
docker stop <container_name_or_id>

# Restart the container
docker restart <container_name_or_id>

All container operations should now work normally.

Advanced notes

Understanding pause vs stop: The docker pause command uses the Linux cgroups freezer subsystem to suspend all processes in a container. This is fundamentally different from docker stop:

| Aspect | docker pause | docker stop |
|--------|--------------|-------------|
| Signal | SIGSTOP (via cgroups) | SIGTERM, then SIGKILL |
| Memory | Preserved | Released |
| State | Frozen in place | Process terminates |
| Resume | Instant (unpause) | Full restart required |
| Network | Connections remain open (but inactive) | Connections closed |

When pausing is useful:
- Temporarily freeing CPU for other tasks while preserving state
- Debugging - freeze a container to inspect its state
- Load balancing - pause containers to shift traffic
- Resource management during peak periods

Paused containers don't survive reboots: Unlike stopped containers which can be started after a system restart, paused containers will be stopped (not paused) after a Docker daemon or system restart. The pause state exists only in memory.

Docker Desktop behavior: On Docker Desktop (Mac/Windows), pausing Docker Desktop itself pauses all containers. Check the Docker Desktop icon in your system tray - if it shows Docker is paused, resume Docker Desktop rather than individual containers.

Monitoring paused containers: You can list only paused containers with:

bash
docker ps --filter "status=paused"

Health checks and paused containers: Container health checks do not run while a container is paused. The health status remains at whatever it was before pausing.

Frequently asked questions

What does "Error response from daemon: container is paused" mean?
This error occurs when you attempt to interact with a Docker container that is currently in a paused state. The full error message typically reads: "Error response from daemon: container is paused" or variations like "Container is paused, unpause the container before exec". When a container is paused, Docker uses the Linux cgroups freezer to suspend all processes inside the container.
How do I fix "Error response from daemon: container is paused"?
The 'container is paused' error occurs when you try to perform operations on a Docker container that has been suspended using the pause command. Simply unpause the container with 'docker unpause' to resume normal operations.
What causes "Error response from daemon: container is paused"?
Container was explicitly paused using 'docker pause' command Docker Compose service was paused using 'docker compose pause' Automated scripts or orchestration tools paused the container
Is the "Error response from daemon: container is paused" error serious?
It is a low-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading