Home / Docker / Fix Docker Pull Timeout Registry Error

Docker

Fix Docker Pull Timeout Registry Error

Fix Docker pull timeout errors from registry-1.docker.io. Resolve network issues, configure mirrors, and pull Docker images successfully.

Published: Apr 27, 20266 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

# Fix Docker Pull Timeout Registry Error

You're trying to pull Docker images but getting timeout errors connecting to registry-1.docker.io or other registries. The pull fails after waiting too long.

Introduction

bash

Error: pull access denied, repository does not exist or may require authorization
net/http: request canceled while waiting for connection (Client.Timeout exceeded)

Docker Hub and other registries can be slow or unreachable due to network issues, rate limiting, or firewall restrictions.

Symptoms

Error messages appear in logs
Service fails to respond correctly
Unexpected behavior in production

Common Causes

Configuration misconfiguration
Resource exhaustion or limits
Network connectivity issues
Permission or access denied

Step-by-Step Fix

Test Registry Connectivity

```bash # Test basic connectivity ping -c 3 registry-1.docker.io

# Test HTTPS curl -I https://registry-1.docker.io/v2/

# Test with verbose curl -v https://registry-1.docker.io/v2/

# Check DNS nslookup registry-1.docker.io dig registry-1.docker.io ```

Check Docker daemon:

```bash # Check Docker status systemctl status docker

# Check Docker info docker info | grep -A 10 "Registry"

# Check Docker logs journalctl -u docker -n 100 ```

Common Causes and Solutions

Cause 1: Network Connectivity Issues

bash

# Error: Connection timed out

Solution:

```bash # Check firewall iptables -L -n | grep 443 firewall-cmd --list-all

# Allow Docker traffic firewall-cmd --add-service=docker --permanent firewall-cmd --reload

# Check proxy settings echo $HTTP_PROXY echo $HTTPS_PROXY

# Configure Docker proxy mkdir -p /etc/systemd/system/docker.service.d cat > /etc/systemd/system/docker.service.d/proxy.conf << 'EOF' [Service] Environment="HTTP_PROXY=http://proxy.example.com:8080" Environment="HTTPS_PROXY=http://proxy.example.com:8080" Environment="NO_PROXY=localhost,127.0.0.1" EOF

systemctl daemon-reload systemctl restart docker ```

Cause 2: DNS Resolution Issues

bash

# Error: Temporary failure in name resolution

Solution:

```bash # Check DNS cat /etc/resolv.conf

# Add Docker DNS servers cat > /etc/docker/daemon.json << 'EOF' { "dns": ["8.8.8.8", "8.8.4.4", "1.1.1.1"] } EOF

systemctl restart docker ```

Cause 3: Docker Hub Rate Limiting

bash

# Error: too many requests, rate limit exceeded

Solution:

```bash # Check rate limit curl -s -H "Authorization: Bearer $(curl -s 'https://auth.docker.io/token?service=registry.docker.io&scope=repository:ratelimitpreview/test:pull' | jq -r .token)" https://registry-1.docker.io/v2/ratelimitpreview/test/manifests/latest -I 2>/dev/null | grep -i ratelimit

# Login to Docker Hub for higher limits docker login

# Or use authenticated pull docker pull -u username -p password myimage ```

Cause 4: Slow Registry Connection

bash

# Error: Timeout waiting for connection

Solution: Use a mirror:

```bash # Configure Docker mirror cat > /etc/docker/daemon.json << 'EOF' { "registry-mirrors": [ "https://mirror.gcr.io", "https://registry.docker-cn.com", "https://docker.mirrors.ustc.edu.cn" ] } EOF

systemctl restart docker ```

Cause 5: MTU Issues

bash

# Error: Connection reset, large images fail

Solution:

```bash # Check MTU ip link show docker0

# Set MTU in Docker config cat > /etc/docker/daemon.json << 'EOF' { "mtu": 1400 } EOF

systemctl restart docker ```

Cause 6: Private Registry Issues

bash

# Error: x509 certificate signed by unknown authority

Solution:

```bash # Add registry to insecure registries cat > /etc/docker/daemon.json << 'EOF' { "insecure-registries": ["registry.example.com:5000"] } EOF

# Or add CA certificate mkdir -p /etc/docker/certs.d/registry.example.com:5000 cp ca.crt /etc/docker/certs.d/registry.example.com:5000/

systemctl restart docker ```

Cause 7: Docker Daemon Issues

bash

# Error: Cannot connect to Docker daemon

Solution:

```bash # Restart Docker systemctl restart docker

# Check Docker socket ls -la /var/run/docker.sock

# Add user to docker group usermod -aG docker $USER

# Check Docker service systemctl status docker ```

Complete Docker Daemon Configuration

json

# /etc/docker/daemon.json
{
  "registry-mirrors": [
    "https://mirror.gcr.io",
    "https://docker.mirrors.ustc.edu.cn"
  ],
  "insecure-registries": ["registry.internal:5000"],
  "dns": ["8.8.8.8", "8.8.4.4"],
  "mtu": 1400,
  "max-concurrent-downloads": 10,
  "max-concurrent-uploads": 5,
  "default-ulimits": {
    "nofile": {
      "Name": "nofile",
      "Hard": 65535,
      "Soft": 65535
    }
  },
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m",
    "max-file": "3"
  }
}

Alternative Solutions

Use Alternative Registry

```bash # Pull from alternative source docker pull quay.io/username/image docker pull gcr.io/project/image docker pull ghcr.io/owner/image

# Tag for local use docker tag quay.io/username/image myimage:latest ```

Save and Load Images

```bash # On machine with access docker pull myimage:latest docker save myimage:latest -o myimage.tar

# Transfer and load on target machine docker load -i myimage.tar ```

Use Docker Registry Cache

```yaml # docker-compose.yml for registry cache version: '3' services: registry: image: registry:2 ports: - "5000:5000" environment: REGISTRY_PROXY_REMOTEURL: https://registry-1.docker.io REGISTRY_STORAGE_CACHE_BLOBDESCRIPTOR: inmemory volumes: - registry-data:/var/lib/registry

volumes: registry-data: ```

```bash # Configure to use local cache cat > /etc/docker/daemon.json << 'EOF' { "registry-mirrors": ["http://localhost:5000"] } EOF

systemctl restart docker ```

Verification

```bash # Test pull docker pull hello-world

# Test with verbose docker pull --debug alpine:latest

# Check registry connectivity curl -I https://registry-1.docker.io/v2/

# Check Docker info docker info

# Test with timeout docker pull --timeout 300 myimage:latest ```

Prevention

1.[ ] Check network connectivity to registry
2.[ ] Verify DNS resolution
3.[ ] Check firewall rules
4.[ ] Configure proxy if needed
5.[ ] Use registry mirrors
6.[ ] Login to Docker Hub for higher rate limits
7.[ ] Check MTU settings
8.[ ] Verify Docker daemon is running
9.[ ] Check certificate issues for private registries
10.[ ] Try alternative registry or save/load method
11.## Common Causes

Configuration misconfiguration
Missing or incorrect credentials
Network connectivity issues
Version compatibility problems
Resource exhaustion or limits
Permission or access denied

[Fix docker build cache invalidated unnecessary layers Issue in Docker-Errors](docker-build-cache-invalidated-unnecessary-layers)
[Fix Docker Build Cache Invalidation Optimization Issue in Docker](docker-build-cache-invalidation-optimization)
[Fix docker build context slow large files Issue in Docker-Errors](docker-build-context-slow-large-files)
[Fix docker build multi stage copy from not found Issue in Docker-Errors](docker-build-multi-stage-copy-from-not-found)
[Fix docker buildkit export local tar layer missing Issue in Docker-Errors](docker-buildkit-export-local-tar-layer-missing)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

Docker Pull Timeout Registry Error Docker Pull Timeout Registry Error Docker Docker Pull Timeout Registry Error troubleshooting Docker Pull Timeout Registry Error fix Fix Docker pull timeout errors from registry-1 Docker Fix Docker pull timeout errors from registry-1

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Docker Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this docker-errors troubleshooting guide applies to my situation?

This guide is designed for docker-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these docker-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of docker-errors issue?

Most docker-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this docker-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for docker-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Apr 27, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Fix Docker Pull Timeout Registry Error

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Test Registry Connectivity

Common Causes and Solutions

Cause 1: Network Connectivity Issues

Cause 2: DNS Resolution Issues

Cause 3: Docker Hub Rate Limiting

Cause 4: Slow Registry Connection

Cause 5: MTU Issues

Cause 6: Private Registry Issues

Cause 7: Docker Daemon Issues

Complete Docker Daemon Configuration

Alternative Solutions

Use Alternative Registry

Save and Load Images

Use Docker Registry Cache

Verification

Prevention

Related Articles

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

Docker Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Fix Docker Pull Timeout Registry Error

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Test Registry Connectivity

Common Causes and Solutions

Cause 1: Network Connectivity Issues

Cause 2: DNS Resolution Issues

Cause 3: Docker Hub Rate Limiting

Cause 4: Slow Registry Connection

Cause 5: MTU Issues

Cause 6: Private Registry Issues

Cause 7: Docker Daemon Issues

Complete Docker Daemon Configuration

Alternative Solutions

Use Alternative Registry

Save and Load Images

Use Docker Registry Cache

Verification

Prevention

Related Articles

People also search for

Share this guide

More Docker Troubleshooting Guides

Browse Guides from Other Categories

Docker Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading