How to fix Error response from daemon: 500 Internal Server Error in Docker

What this error means

The "500 Internal Server Error" from the Docker daemon indicates that an unexpected condition occurred that prevented the Docker daemon or a remote registry from fulfilling your request. Unlike more specific errors, a 500 error is a generic "something went wrong on the server side" message that requires investigation to determine the root cause. This error commonly appears in several scenarios: - **Image pull/push operations**: When Docker Hub or a private registry experiences temporary issues or outages - **Local registry operations**: When your self-hosted registry runs out of disk space, has permission issues, or misconfigured storage backends - **Docker API requests**: When the Docker daemon cannot respond properly due to resource exhaustion or internal state corruption - **CI/CD pipelines**: When registry operations fail due to network issues, rate limits, or transient server problems The 500 error is particularly frustrating because it doesn't tell you exactly what went wrong - you'll need to check daemon logs, registry logs, and system resources to diagnose the underlying issue.

Typical symptoms

• Docker pull fails with 'Error response from daemon: 500 Internal Server Error'
• Docker push operations fail intermittently with HTTP 500
• Docker commands hang and eventually return 500 errors
• CI/CD pipelines fail during image pull or push steps
• Docker API requests return HTTP status 500
• Registry operations fail but work again after retry
• Docker login fails with 500 Internal Server Error

Common causes

1. Docker Hub or container registry experiencing temporary outage
2. Insufficient disk space on registry server or Docker host
3. Storage driver errors or corruption (overlay2, devicemapper, etc.)
4. Docker daemon resource exhaustion (memory, file descriptors)
5. Permission issues on registry storage backend
6. Nginx or reverse proxy in front of registry has misconfiguration
7. Registry running out of temporary file space during layer uploads
8. Network proxy or firewall interfering with large file transfers
9. TLS certificate issues between Docker client and registry
10. Corrupted or incomplete image layers on the registry

How to fix "Error response from daemon: 500 Internal Server Error"

# Wait and retry the operation
sleep 60
docker pull nginx:latest

# View recent Docker daemon logs
sudo journalctl -u docker.service --since "10 minutes ago"

# Follow logs in real-time
sudo journalctl -u docker.service -f

# Check various log locations
tail -100 /var/log/docker.log
tail -100 /var/log/daemon.log
grep docker /var/log/messages

# Add to /etc/docker/daemon.json
{
  "debug": true
}

# Restart Docker
sudo systemctl restart docker

# Check overall disk usage
df -h

# Check Docker-specific disk usage
docker system df

# See detailed breakdown
docker system df -v

# Remove unused containers, networks, images, and build cache
docker system prune -a

# Also remove unused volumes (careful - this deletes data!)
docker system prune -a --volumes

# Remove specific resources
docker container prune   # Remove stopped containers
docker image prune -a    # Remove unused images
docker volume prune      # Remove unused volumes

# SSH to registry server
df -h /var/lib/registry

# Run garbage collection if using Docker Registry
docker exec registry bin/registry garbage-collect /etc/docker/registry/config.yml

# Test from host
nslookup registry-1.docker.io
dig registry-1.docker.io

# Test from a container
docker run --rm alpine nslookup registry-1.docker.io

# Edit /etc/docker/daemon.json
sudo tee /etc/docker/daemon.json << EOF
{
  "dns": ["8.8.8.8", "8.8.4.4"]
}
EOF

# Restart Docker
sudo systemctl restart docker

docker run --dns 8.8.8.8 --dns 8.8.4.4 myimage

# Edit /etc/docker/daemon.json (Linux)
# or C:\ProgramData\Docker\config\daemon.json (Windows)
{
  "allow-nondistributable-artifacts": ["myregistry.example.com:5000"]
}

# Linux
sudo systemctl restart docker

# Windows (PowerShell as Administrator)
Restart-Service docker

# In your nginx.conf or site config
server {
    listen 443 ssl;
    server_name registry.example.com;

    # Increase max body size for large layers
    client_max_body_size 0;  # 0 = no limit

    # Increase timeouts for slow uploads
    proxy_connect_timeout 900;
    proxy_send_timeout 900;
    proxy_read_timeout 900;

    # Disable buffering for large files
    proxy_buffering off;
    proxy_request_buffering off;

    location / {
        proxy_pass http://registry:5000;
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

# Nginx stores request bodies in temp directory
df -h /var/lib/nginx/tmp
# or
df -h /var/cache/nginx

docker info | grep "Storage Driver"

# Check for filesystem errors
sudo dmesg | grep -i "overlay\|ext4\|xfs"

# Verify overlay module is loaded
lsmod | grep overlay

# Check thin pool space
docker info | grep -i "pool\|data\|metadata"

# If thin pool is full, extend it or prune
docker system prune -a

# WARNING: This removes all containers and images!
# Stop Docker
sudo systemctl stop docker

# Remove Docker data directory
sudo rm -rf /var/lib/docker

# Restart Docker (will recreate with fresh storage)
sudo systemctl start docker

# Linux
sudo systemctl restart docker

# Check it's running properly
sudo systemctl status docker
docker info

# Stop Docker
sudo systemctl stop docker

# Clear Docker state (preserves images/containers)
sudo rm -f /var/run/docker.pid
sudo rm -f /var/run/docker.sock

# Start Docker
sudo systemctl start docker

# Check for zombie processes
ps aux | grep -i docker

# Kill stuck processes if necessary
sudo pkill -9 -f dockerd
sudo systemctl start docker

# Logout first
docker logout

# Login again
docker login

# Test a pull
docker pull hello-world

docker logout myregistry.example.com
docker login myregistry.example.com

# View Docker config
cat ~/.docker/config.json

# If using credential helpers, verify they work
docker-credential-desktop list  # macOS/Windows
docker-credential-secretservice list  # Linux

Advanced notes

# View registry logs
docker logs registry 2>&1 | tail -100

# Enable debug logging in registry config
# /etc/docker/registry/config.yml
log:
  level: debug
  formatter: text

# config.yml - add logging
storage:
  s3:
    accesskey: ...
    secretkey: ...
    region: us-east-1
    bucket: my-registry-bucket
  # Add maintenance to check storage health
  maintenance:
    uploadpurging:
      enabled: true
      age: 168h
      interval: 24h
      dryrun: false

#!/bin/bash
MAX_RETRIES=3
RETRY_DELAY=30

for i in $(seq 1 $MAX_RETRIES); do
  docker pull myimage:latest && break
  echo "Attempt $i failed, waiting ${RETRY_DELAY}s..."
  sleep $RETRY_DELAY
done

# Check file descriptor limits
cat /proc/$(pidof dockerd)/limits | grep "open files"

# Increase if needed in /etc/security/limits.conf
* soft nofile 65536
* hard nofile 65536

# Check kernel messages for Docker-related errors
dmesg | grep -i "docker\|overlay\|cgroup"

# Check if required kernel modules are loaded
lsmod | grep -E "overlay|br_netfilter|ip_tables"

Frequently asked questions

What does "500" mean?

The "500 Internal Server Error" from the Docker daemon indicates that an unexpected condition occurred that prevented the Docker daemon or a remote registry from fulfilling your request. Unlike more specific errors, a 500 error is a generic "something went wrong on the server side" message that requires investigation to determine the root cause. This error commonly appears in several scenarios: - Image pull/push operations: When Docker Hub or a private registry experiences temporary issues or outages - Local registry operations: When your self-hosted registry runs out of disk space, has permission issues, or misconfigured storage backends - Docker API requests: When the Docker daemon cannot respond properly due to resource exhaustion or internal state corruption - CI/CD pipelines: When registry operations fail due to network issues, rate limits, or transient server problems The 500 error is particularly frustrating because it doesn't tell you exactly what went wrong - you'll need to check daemon logs, registry logs, and system resources to diagnose the underlying issue.

How do I fix "500"?

This error occurs when the Docker daemon or a container registry encounters an internal failure. Common causes include registry issues, disk space problems, storage driver errors, or daemon resource exhaustion.

What causes "500"?

Docker Hub or container registry experiencing temporary outage Insufficient disk space on registry server or Docker host Storage driver errors or corruption (overlay2, devicemapper, etc.)

Is the "500" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• Error response from daemon: invalid argument

  How to fix 'invalid argument' in Docker

  MEDIUM

• Error response from daemon: Get https://myregistry:5000/v2/: http: server gave HTTP response to HTTPS client

  How to fix 'server gave HTTP response to HTTPS client' in Docker

  MEDIUM

• Dockerfile parse error line 10: MAINTAINER is deprecated

  How to fix 'MAINTAINER is deprecated' in Docker

  LOW

• OCI runtime create failed: container init process failed

  How to fix 'OCI runtime create failed: container init process failed' in Docker

  HIGH

• WSL 2 requires an update to its kernel component

  How to fix 'WSL 2 requires an update to its kernel component' in Docker

  MEDIUM

• dial tcp: i/o timeout

  How to fix 'dial tcp: i/o timeout' in Docker

  MEDIUM

Official resources & further reading

• 📚Docker Official Documentation
• 📖
  Read the daemon logs - Docker Docs(Official Docs)
• 📖
  Troubleshoot and diagnose - Docker Desktop Docs(Official Docs)
• 💬
  Docker Windows Local Registry: 500 Internal Server Error - Stack Overflow(Stack Overflow)
• 💬
  Request returned 500 Internal Server Error for API route - Docker Forums(Stack Overflow)
• 🐙
  docker pull by sha256 leads to 500 Internal Server Error - GitHub(GitHub)
• 🐙
  docker login fails with 500 Internal server error and EOF - GitHub(GitHub)
• 💬
  Push to Docker Hub fails with 500 Internal Server Error - Server Fault(Stack Overflow)
• 📖
  How to Access and Understand Docker Daemon Logs - SigNoz(Official Docs)