Network timed out while trying to connect to https://index.docker.io

前端 未结 19 1514
执念已碎
执念已碎 2021-01-29 17:27

I installed Docker-Toolbox just now while following their webpage

I started with Docker QuickStart Terminal and see following

                      


        
相关标签:
19条回答
  • 2021-01-29 18:09

    In my case, installing docker on Alpine Linux I get the error:

    Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/........

    Using the script here: https://github.com/docker/docker/blob/master/contrib/download-frozen-image-v2.sh

    Works. It downloads the image using curl and then shows you how to untar and 'docker load' it.

    I tried the above methods of static DNS at 8.8.8.8 and disabling ipv6 (I didn't understand the proxy thing) and none of them worked for me.

    EDIT 9/8/2016:

    I was initially using dropbear instead of openssh. Reinstalled Alpine with openssh fixed the problem.

    The next problem was 'ApplyLayer exit status 1 stdout: stderr: chmod /bin/mount: permission denied' error during pull.

    From (nixaid.com/grsec-in-docker/):

    To build the Docker image, I had to disable the following grsec protections. Modify the /etc/sysctl.d/grsec.conf as follows:

    kernel.grsecurity.chroot_deny_chmod = 0 kernel.grsecurity.chroot_deny_mknod = 0 kernel.grsecurity.chroot_caps = 0 # related to a systemd package/CAP_SETFCAP

    in alpine's case though it's

    /etc/sysctl.d/00-alpine.conf

    reboot

    0 讨论(0)
  • 2021-01-29 18:11

    I ran into this exact same problem yesterday and none of the "popular" answers (like fixing DNS to 8.8.8.8) worked for me. I eventually happened across this link, and that did the trick ... https://github.com/docker/for-win/issues/16

    Between Docker for Windows, Windows 10 and Hyper-V, there seems to be a problem during the virtual network adapter creation process. Specifically, you might end up with two "vEthernet (DockerNAT)" network adapters. Check this with Get-NetAdapter "vEthernet (DockerNAT)" (in an elevated PowerShell console). If the result shows more than one adapter, you can disable and rename it with:

    $vmNetAdapter = Get-VMNetworkAdapter -ManagementOS -SwitchName DockerNAT
    Get-NetAdapter "vEthernet (DockerNAT)" | ? { $_.DeviceID -ne $vmNetAdapter.DeviceID } | Disable-NetAdapter -Confirm:$False -PassThru | Rename-NetAdapter -NewName "OLD"
    

    Then open up Device Manager and delete the disabled adapter (for some reason you can do this from here, but not from the Network and Sharing Center adapters view).

    0 讨论(0)
  • 2021-01-29 18:14

    I just ran into this today with 1.10.1 and none of the existing solutions worked. I tried to restart, upgrade, regenerate certs, ...

    I noticed that I had a lot of networks created on the machine. After removing them with:

    docker network ls | grep bridge | awk '{print $1}' | xargs -n1 docker network rm
    

    The DNS started working again.

    Note: You may ignore errors about pre-defined networks

    0 讨论(0)
  • 2021-01-29 18:16

    I assume that you have a network problem. Are you behind a proxy? Is it possible that it filters the connection to docker.io or blocks the docker user agent?

    I installed the toolbox and ran your test. It works fine, here:

    docker is configured to use the default machine with IP 192.168.99.101
    For help getting started, check out the docs at https://docs.docker.com
    
    bash-3.2$ docker run hello-world
    Unable to find image 'hello-world:latest' locally
    latest: Pulling from library/hello-world
    
    535020c3e8ad: Pull complete 
    af340544ed62: Already exists 
    library/hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
    Digest: sha256:d5fbd996e6562438f7ea5389d7da867fe58e04d581810e230df4cc073271ea52
    Status: Downloaded newer image for hello-world:latest
    
    Hello from Docker.
    This message shows that your installation appears to be working correctly.
    
    To generate this message, Docker took the following steps:
     1. The Docker client contacted the Docker daemon.
     2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
     3. The Docker daemon created a new container from that image which runs the
        executable that produces the output you are currently reading.
     4. The Docker daemon streamed that output to the Docker client, which sent it
        to your terminal.
    
    To try something more ambitious, you can run an Ubuntu container with:
     $ docker run -it ubuntu bash
    
    Share images, automate workflows, and more with a free Docker Hub account:
     https://hub.docker.com
    
    For more examples and ideas, visit:
     https://docs.docker.com/userguide/
    
    bash-3.2$
    
    0 讨论(0)
  • 2021-01-29 18:16

    Create a systemd drop-in directory for the docker service:

    $ sudo mkdir -p /etc/systemd/system/docker.service.d
    

    Create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable:

    [Service]

    Environment="HTTP_PROXY=http://proxy.example.com:80/"
    

    Hope it helps

    0 讨论(0)
  • 2021-01-29 18:18

    On Windows this happened when I moved from a work network to a home network.

    To solve it, run:

    1. docker-machine stop
    2. docker-machine start
    3. docker-env
    4. "C:\Program Files\Docker Toolbox\docker-machine.exe" env | Invoke-Expression
    0 讨论(0)
提交回复
热议问题