Pulling images impossible: Unexpected EOF

gingters commented 4 years ago

[X] I have tried with the latest version of my channel (Stable or Edge)
[X] I have uploaded Diagnostics
Diagnostics ID: FDE7E224-A933-4E0F-94F5-5BA825FF2155/20200401125255

Expected behavior

docker run hello-world should run.

Actual behavior

Docker fails at pulling the image with an unexpected EOF error:

PS C:\Dev> docker run hello-world
Unable to find image 'hello-world:latest' locally
C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: Get https://registry-1.docker.io/v2
/library/hello-world/manifests/latest: Get https://auth.docker.io/token?scope=repository%3Alibrary%2Fhello-world%3Apull&
service=registry.docker.io: unexpected EOF.

This does also happen when downloading from other registries:

PS C:\Dev> docker pull mcr.microsoft.com/mssql/server:2019-latest
Error response from daemon: Get https://mcr.microsoft.com/v2/mssql/server/manifests/2019-latest: unexpected EOF

Information

Is it reproducible? Yes.
Is the problem new? Yes.
Did the problem appear with an update? Probably. I could pull images bevor. But I can't tell when this was introduced.
Windows Version: 1909 Build 18363.752
Docker Desktop Version: 2.2.0.4 (43472)
Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Additional Info:

I already tried:

uninstalling Docker Desktop & reinstalling
- Both Edge as well as Stable
Reset to factory defaults
Login with my dockerhub credentials
logout again

There are different unexpected EOF issues on the community and here, but no answers:

This is a complete showstopper, as reinstalling and factory reset of course cleared all images, and now I can't run anything on docker anymore.

hgross commented 4 years ago

I have the same issue: Windows 10 over 1GBit ethernet via 500 MBit UnityMedia (Vodafone) - FRITZ!Box 6591 Cable - FRITZ!OS 07.13 - DSLite connection

I operate my own FRITZ!Box 6591 Cable (not provided by Vodafone, Routerfreiheit) and updated to the new 7.21 release - this fixed the issues for me. I have hardware acceleration enabled.

emuuu commented 4 years ago

(not provided by Vodafone, Routerfreiheit)

Well Routerfreiheit is pretty much of a joke in this context as Vodafone only grants you static public IP(s) if you use their router. If you want to use your own u automatically fallback to a dynamic IP (they don't tell you that in advance tho)

I've just configured the FritzBox to be just a gateway for my Linksys router. This seems to fix the problem as well. Just pulled a mongo image without any problems.

VanillaFord commented 4 years ago

I do have that problem, although using a MikroTik external router behind the Fritz (VF 6951), that is configured as exposed host. The only way for me to solve this, is not to use Windows anymore, as pulling imgaes via my Liniux based NAS is possible.

hgross commented 4 years ago

(not provided by Vodafone, Routerfreiheit)

Well Routerfreiheit is pretty much of a joke in this context as Vodafone only grants you static public IP(s) if you use their router. If you want to use your own u automatically fallback to a dynamic IP (they don't tell you that in advance tho)

I've just configured the FritzBox to be just a gateway for my Linksys router. This seems to fix the problem as well. Just pulled a mongo image without any problems.

Yeah, for me even getting a static IP wasn't possible anymore in 12/2019 - only DSLite for newly connected houses. Of course I filed a complaint with the agency. BTW: The "static-ip gap" can be somewhat (significant performance loss) bridged using a cheap vServer with a static ip which routes through a VPN into your home network.

alxbauer commented 4 years ago

Same story! FritzBox 6591, Vodafone, OS 07.13. Thanks a lot for sharing the workaround!

thomasjungblut commented 4 years ago

Recently my FritzBox 6660 updated to 07.21, which fixed the issue for me.

I realize that I'm late to the party, but indeed the update to 07.21 fixed it (6591 cable). What a crazy issue! Is there more information on what the issue was from Fritz!OS point of view?

thimo-seitz commented 4 years ago

Nothing specific in the changelog. Maybe that entry: grafik

Nowi5 commented 3 years ago

Had the same issue. Thank you for your support. Still waiting for my update (vodafone/unitymedia)

jsteenri commented 3 years ago

I encountered this same issue as well from the Americas with no FritzBox! in sight. Ensuring that the docker pull was not going though a proxy server solved the problem for me.

Specifically, in Docker Desktop Settings ==> Resources ==> Proxies, either don't define one, or add exceptions as needed.

Note: when working with the new GitHub Container Registry, I found I needed both ghcr.io and github-production-container-registry.s3.amazonaws.com in the exception list.

VinzSpring commented 3 years ago

I encountered a similar issue where I couldn't pull any images from docker. Deactivating the Vodafone-Gateway's Internal Firewall fixed the issue! 👍

Day0Dreamer commented 3 years ago

@VinzSpring - How did you do that? Also - VPN helped

jmartsch commented 3 years ago

I have the same issue: Windows 10 over 1GBit ethernet UnityMedia (Vodafone) - FRITZ!Box 6591 Cable - FRITZ!OS 7.13.

The problem is, that Vodafone/Unitymedia did not update the firmware to 7.20 which was released 3 months ago. There is a long german thread about this issue here https://forum.vodafone.de/t5/Internet-Ger%C3%A4te/Kein-Update-bei-FritzBox-6591-Cable/td-p/2421100 and it really makes me angry, that such important updates take such a long time.

VinzSpring commented 3 years ago

@Day0Dreamer via the router's webinterface.

robinduerhager commented 3 years ago

Same Issue here! FRITZ!Box 6591 Cable with FRITZ!OS 07.13 (1GBit ethernet UnityMedia (Vodafone)) and Docker Desktop version 3.0.0 (50684) on Windows 10 Pro (19041.685).

Disabling Hardware acceleration is a valid workaround for now. Hope Vodafone is rolling out a new FRITZ!OS Update soon.

gururajn commented 3 years ago

I'm having similar issue when I execute the build command docker-compose -f docker-compose.yml up -d --build ERROR: unexpected EOF docker info `Client: Context: default Debug Mode: false Plugins: app: Docker App (Docker Inc., v0.9.1-beta3) buildx: Build with BuildKit (Docker Inc., v0.5.1-docker) scan: Docker Scan (Docker Inc., v0.5.0)

Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 2 Server Version: 20.10.2 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff init version: de40ad0 Security Options: seccomp Profile: default Kernel Version: 4.19.121-linuxkit Operating System: Docker Desktop OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 1.944GiB Name: docker-desktop ID: RCN6:FCOB:GC44:2O6T:Z67C:6THC:QAUM:QRU6:VQ7L:AYMK:GVFR:TAPE Docker Root Dir: /var/lib/docker Debug Mode: false HTTP Proxy: gateway.docker.internal:3128 HTTPS Proxy: gateway.docker.internal:3129 Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false`

khamza85 commented 3 years ago

Getting the same error after I changed --data-rootfromC:\toD:\disk. My router is InnboxG74 and not from Germany.

shivan commented 3 years ago

fyi: Today I got the Update 7.22 from Vodafone on my FritzBox 6591

VanillaFord commented 3 years ago

...this update seems to be directed towards Unitymedia boxes only, see: https://www.vodafonekabelforum.de/viewtopic.php?f=67&t=43570 (VF-West) Regular VF users will still have to wait ;-(

fabianblum commented 3 years ago

If you have Fritz!Box. Disable "Hardware acceleration". After you logged in click on the bottom side on "Content" and then on "Fritz!Box Support" then scroll to "Packet acceleration" and disable it. Save and it should work now

sschuberth commented 3 years ago

Thanks @fabianblum. However, that was already described in a comment above 😉

busaku commented 3 years ago

Worked. But lost 700Mbits download.

dfyx commented 3 years ago

...this update seems to be directed towards Unitymedia boxes only, see: https://www.vodafonekabelforum.de/viewtopic.php?f=67&t=43570 (VF-West) Regular VF users will still have to wait ;-(

Even worse: only Unitymedia boxes with dynamic IP addresses. Business customers with static IP addresses (like me) will have to wait until late April, according to the hotline.

ColinCee commented 3 years ago

Fixed a similar issue when I tried setting up WSL2 with docker today.

$ docker-compose up
Pulling db (mongo:4.4-bionic)...
ERROR: Get https://registry-1.docker.io/v2/: EOF
$ cat ~/.docker/config.json 
{
        "auths": {
                "https://index.docker.io/v1/": {}
        },
        "credsStore": "desktop.exe"
}

I had an existing WSL2 with docker installation working fine so I compared the config.json and deleted the auths so that it looks like this:

{
        "auths": {},
        "credsStore": "desktop.exe"
}

VanillaFord commented 3 years ago

fyi: Today I got the Update 7.22 from Vodafone on my FritzBox 6591

fwiw: ....VF pushed v7.21 (note, not 7.22 like with ex-unitymedia boxes) to my Homebox 6591Cable about 10 days ago and I've been pulling my hair out since then. First I had to perform a factory reset in order from preventing the box to reboot every 15 mins. Second, the LAN-Switch is showing port-flaps, where the link will go offline for about 3-4secs.....never had this with v7.13 and earlier, but as it turns out this is an incompatibility with my main switch and router, a mikrotik RB4011...after moving the port into a VLAN on my Mikrotik CRS326 switch, this is now stable again.

...sorry for OT.

jmartsch commented 3 years ago

fyi: Today I got the Update 7.22 from Vodafone on my FritzBox 6591

fwiw: ....VF pushed v7.21 (note, not 7.22 like with ex-unitymedia boxes) to my Homebox 6591Cable about 10 days ago and I've been pulling my hair out since then. First I had to perform a factory reset in order from preventing the box to reboot every 15 mins. Second, the LAN-Switch is showing port-flaps, where the link will go offline for about 3-4secs.....never had this with v7.13 and earlier, but as it turns out this is an incompatibility with my main switch and router, a mikrotik RB4011...after moving the port into a VLAN on my Mikrotik CRS326 switch, this is now stable again.

...sorry for OT.

Everything worked fine here, as soon as my router had the update.

docker-robott commented 3 years ago

Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale

dfyx commented 3 years ago

Vodafone has updated all routers by now so I'd say this can be closed.

docker-robott commented 3 years ago

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

docker / for-win