lookup registry-1.docker.io: no such host Docker Origin: Platform & cloud OSI layer 7 · Application Last updated 15 Oct 2026

dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build

DNS isn’t working for the Docker daemon or inside build containers, so pulls and package downloads fail.

Exact message you may see lookup registry-1.docker.io: no such hostTemporary failure resolvingTemporary failure in name resolutiondial tcp: lookup
Seen on: Docker

Meaning

Containers copy DNS settings from the host, but systemd-resolved (127.0.0.53), VPN DNS and corporate DNS often don’t work from inside containers. apt-get update then shows “Temporary failure resolving 'deb.debian.org'”, and FROM fails with “no such host”.

Common causes

  • Host uses a local resolver (127.0.0.53) unreachable from containers
  • VPN/corporate DNS not forwarded to Docker
  • Network down or proxy required
  • Docker Desktop VM DNS glitch

⚡ Quick fix

  1. Set DNS servers in daemon.json and restart Docker
  2. Build with --network host as a test
  3. Restart Docker Desktop

Detailed fix by platform

Docker

  1. bash
    # /etc/docker/daemon.json
    { "dns": ["1.1.1.1", "8.8.8.8"] }
    sudo systemctl restart docker
    docker run --rm busybox nslookup deb.debian.org

How to diagnose

  1. Container DNS — docker run --rm busybox cat /etc/resolv.conf
  2. Lookup — docker run --rm busybox nslookup google.com
  3. Proxy — Is one required?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

0x80072EE7 — Error 0x80072EE7 (Windows Update / Microsoft Store: server name could not be resolved) (Windows)0x80072EE71000 — Cloudflare Error 1000: DNS points to prohibited IP (Cloudflare)10001001 — Cloudflare Error 1001: DNS resolution error (Cloudflare)100114 UNAVAILABLE — gRPC Error: 14 UNAVAILABLE: No connection established / failed to connect to all addresses (API)14 UNAVAILABLE2003 — MySQL ERROR 2003 (HY000): Can't connect to MySQL server on 'host:3306' (111) (MySQL)2003408 — HTTP 408 Request Timeout (HTTP)408AbortError — AbortError: The user aborted a request. / signal is aborted without reason (JavaScript)AbortErrorauth/network-request-failed — Firebase Auth: auth/network-request-failed — A network AuthError (such as timeout, interrupted connection or unreachable host) has occurred (Authentication)auth/network-request-…lookup re…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.