How to fix docker: Error response from daemon (exit status 125) in Docker

First, verify the Docker daemon is active and responding:

# On Linux
sudo systemctl status docker

# Or try
docker info

If Docker is not running, start it:

# On Linux
sudo systemctl start docker

# On Mac/Windows
# Start Docker Desktop application

Execute your docker run command directly in the terminal to see the complete error message. Exit code 125 is generic, but the accompanying message reveals the actual problem:

docker run [your-options] [image-name]

Look for specific errors like:
- "Conflict. The container name is already in use"
- "Invalid address X.X.X.X: It does not belong to any of this network's subnets"
- "Range of CPUs is from 0.01 to X.XX, as there are only X CPUs available"
- "user declined directory sharing"

If the error mentions a container name conflict, list and remove the existing container:

# List all containers (including stopped ones)
docker ps -a

# Remove the conflicting container
docker rm <container-name>

# Or remove all stopped containers
docker container prune

To prevent this issue, use the --rm flag to automatically remove containers on exit:

docker run --rm [other-options] [image-name]

Check if the Docker image exists locally:

docker images

If the image is missing (possibly removed by docker system prune), pull it again:

docker pull [image-name]

If the error mentions network problems:

# List networks
docker network ls

# Inspect the network
docker network inspect [network-name]

# Remove and recreate if needed
docker network rm [network-name]
docker network create [network-name]

If manually specifying an IP address, ensure it belongs to the network's subnet range.

On Windows or Mac, if you see "user declined directory sharing":

1. Open Docker Desktop
2. Go to Settings → Resources → File Sharing
3. Add the directory path that contains your volumes or bind mounts
4. Click "Apply & Restart"

On Windows, ensure the drive is shared in Docker Desktop settings.

If the error mentions CPU constraints, either:

Option 1: Reduce the CPU limit in your docker run command:

docker run --cpus="1.0" [image-name]

Option 2: Increase Docker Desktop's CPU allocation (Mac/Windows):
1. Open Docker Desktop → Settings → Resources
2. Increase CPUs and Memory sliders
3. Apply & Restart

If none of the above work, try resetting Docker:

# Restart Docker daemon (Linux)
sudo systemctl restart docker

# Or reset containers and networks
docker container prune
docker network prune
docker volume prune

On Docker Desktop (Mac/Windows), use "Troubleshoot → Reset to factory defaults" as a last resort (this will remove all containers, images, and volumes).