Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pulling images sometimes gets stuck #813

Open
UriShohet opened this issue Jun 12, 2017 · 59 comments
Open

pulling images sometimes gets stuck #813

UriShohet opened this issue Jun 12, 2017 · 59 comments

Comments

@UriShohet
Copy link

Expected behavior

docker pull redis:latest
should pull the image.
same for docker pull mongo:3.2
docker run hello-world pulls and runs the container successfully

Actual behavior

Pull gets stuck:

3.2: Pulling from library/mongo
56c7afbcb0f1: Pull complete
ac4863389b54: Pull complete
91c243d2b8e5: Pull complete
a4a58b6a7bcb: Pull complete
9d61ffb46087: Pull complete
eb30575dc34c: Pull complete
f12530a3e445: Pull complete
73ef25d9b6d8: Downloading [==>                                                ] 1.507 MB/37.54 MB
67152c76660b: Download complete
2ac4b00574a5: Download complete
9b29499d466e: Download complete

Information

  • Diagnostic ID from "Diagnose & Feedback" in the menu.
    01FBB77B-D542-4FD5-BA74-DFA1DEDEC377/2017-06-12_16-53-15
  • a reproducible case if this is a bug, Dockerfiles FTW
  • page URL if this is a docs issue or the name of a man page
  • host distribution and version (Windows version, build number, etc)
    Windows 10 Enterprise
    Version 1511
    OS Build 10586.916

docker info output:

Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 8
Server Version: 17.03.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.27-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.941 GiB
Name: moby
ID: DLPG:53MD:L7OV:4KSQ:5FPW:5ILI:CJ67:IXN5:RD5T:WYEA:6UQE:2F77
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 25
 Goroutines: 58
 System Time: 2017-06-12T14:03:00.6836034Z
 EventsListeners: 0
Http Proxy: http://proxy.iil.intel.com:911
Https Proxy: http://proxy.iil.intel.com:911
No Proxy: *.intel.com,intel.com,localhost,127.0.0.1
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 blahblah.blah.intel.com:5000
 127.0.0.0/8
Live Restore Enabled: false

Steps to reproduce the behavior

  1. ...
  2. ...
@UriShohet
Copy link
Author

I also saw the following in the log when it's stuck, no idea if this is related/helpful:

[17:20:53.338][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 2b2168a2-e881-4af9-8ba6-56f83a1b9b90:23a432c2-537a-4291-bcb5-d62504644739
[17:20:59.362][VpnKit         ][Error  ] com.docker.slirp.exe: PPP.listen callback caught (Invalid_argument
[17:20:59.362][VpnKit         ][Info   ]   "Cstruct.blit src=[25929,1360](65536) dst=[0,4096](4096) dst-off=3072 len=1360")
[17:21:07.123][VpnKit         ][Error  ] com.docker.slirp.exe: Lwt.async failure (Invalid_argument
[17:21:07.123][VpnKit         ][Info   ] Tcp.PCB: ERROR: thread failure; terminating threads and closing connection
[17:21:07.123][VpnKit         ][Info   ]   "Cstruct.blit src=[23568,1360](65536) dst=[0,4096](4096) dst-off=2808 len=1360"): Raised at file "format.ml", line 241, characters 41-52
[17:21:07.123][VpnKit         ][Info   ] Called from file "format.ml", line 482, characters 6-24
[17:21:07.123][VpnKit         ][Info   ]
[17:21:09.154][VpnKit         ][Info   ] Tcp.Segment: TCP retransmission on timer seq = 457836693
[17:21:11.155][VpnKit         ][Info   ] Tcp.Segment: TCP retransmission on timer seq = 457836693

@synergiator
Copy link

similar behaviour:
moby/moby#34080

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d 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

@hervinhio
Copy link

/remove-lifecycle stale

@hervinhio
Copy link

Facing the same issue over here.

@MatthewLymer
Copy link

MatthewLymer commented Jun 26, 2018

Same issue for me:

> docker pull microsoft/dotnet:2.1-sdk
2.1-sdk: Pulling from microsoft/dotnet
cc1a78bfd46b: Pull complete
d2c05365ee2a: Pull complete
231cb0e216d3: Pull complete
3d2aa70286b8: Downloading [=====================================>             ]  37.64MB/50.06MB
07efaf3b1df1: Waiting
2986ca0b5138: Waiting
21ad545f7af9: Waiting

@MatthewLymer
Copy link

MatthewLymer commented Jun 28, 2018

I found that, at least on Windows 10, that if a docker gets stuck downloading an image, I'm able to force-quit the vpnkit.exe application in Task Manager. The download will resume in approximately 15 seconds afterwards. I'll have to restart docker afterwards to get networking to work properly, but at least it'll let me download all the images I need for next time.

EDIT:
Please see #813 (comment) by @AdityaNikhil as well if this doesn't work for you.

@akramul-hasan-m4
Copy link

Same issue for me. every time i try and try but same result. i am using windows 10 :

$ docker pull mysql:5.7
5.7: Pulling from library/mysql
683abbb4ea60: Pull complete
0550d17aeefa: Pull complete
7e26605ddd77: Downloading [===========> ] 1.035MB/4.499MB
9882737bd15f: Download complete
999c06ab75f6: Download complete
c71d695f9937: Download complete
c38f847c1491: Download complete
74f9c61f40bf: Download complete
30b252a90a12: Download complete
9f92ebb7da55: Download complete
90303981d276: Download complete

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d 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

@andreminelli
Copy link

Same here:

C:\Windows\system32>docker pull microsoft/dotnet-framework:4.6.2-runtime-windowsservercore-ltsc2016
4.6.2-runtime-windowsservercore-ltsc2016: Pulling from microsoft/dotnet-framework
3889bb8d808b: Downloading [=====================> ] 1.727GB/4.07GB
c0f6863f3dd4: Download complete
fb72e3c6589b: Download complete
65e1c033c2eb: Download complete

Report Id: 61D96729-F48C-4746-8036-A3DE264B6608/20181018110138
OS: Windows 10
Docker version: 18.06.1-ce

@andreminelli
Copy link

Disabling the antivirus solved this issue for me.

@hervinhio
Copy link

Until now all we've seen are workarounds and the best is probably the one from @MatthewLymer

@igorgatis
Copy link

Same problem running docker run -it --privileged -p 8443:8443 -p 10080:10080 bsycorp/kind:v1.11.5

image

docker info:

Containers: 2
 Running: 2
 Paused: 0
 Stopped: 0
Images: 7
Server Version: 18.09.1
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 96ec2177ae841256168fcf76954f7177af9446eb
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.14.92-boot2docker
Operating System: Boot2Docker 18.09.1 (TCL 8.2.1)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.793GiB
Name: dockervm
ID: SLMT:XAKV:SG7B:XBV5:6VL5:BKI2:73AD:JI2O:POY6:KCT7:GYU6:FAUP
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

@duncanphillips
Copy link

still happening.

I'm running from minikube

3.7.2-slim-stretch: Pulling from library/python
5e6ec7f28fb7: Pull complete
93bed770c432: Downloading [======================>                            ]  1.154MB/2.528MB
05cc6acbde1c: Download complete
2e7e7b22736c: Download complete
e13141912ca4: Download complete

@mikebollandajw
Copy link

mikebollandajw commented Feb 8, 2019

also having this with docker + windows 2016 ami on aws

same image microsoft/dotnet-framework:4.6.2-runtime

C:\test\QuantumAPI\QuantumAPI>docker build .
Sending build context to Docker daemon 3.072 kB
Step 1/5 : FROM microsoft/dotnet-framework:4.6.2-runtime
4.6.2-runtime: Pulling from microsoft/dotnet-framework

3889bb8d808b: Already exists
d0c71fc8924e: Extracting [=================================>                 ] 1.041 GB/1.566 GB
a13e6b26f7d9: Download complete
6ea9c263f713: Download complete

C:\test\QuantumAPI\QuantumAPI>
C:\test\QuantumAPI\QuantumAPI>
C:\test\QuantumAPI\QuantumAPI>
C:\test\QuantumAPI\QuantumAPI>docker build .
Sending build context to Docker daemon 3.072 kB
Step 1/5 : FROM microsoft/dotnet-framework:4.6.2-runtime
4.6.2-runtime: Pulling from microsoft/dotnet-framework

3889bb8d808b: Already exists
d0c71fc8924e: Extracting [=================================================> ] 1.554 GB/1.566 GB
a13e6b26f7d9: Download complete
6ea9c263f713: Download complete

C:\test\QuantumAPI\QuantumAPI>docker build .
Sending build context to Docker daemon 3.072 kB
Step 1/5 : FROM microsoft/dotnet-framework:4.6.2-runtime
4.6.2-runtime: Pulling from microsoft/dotnet-framework
3889bb8d808b: Already exists
d0c71fc8924e: Extracting [=================================>                 ] 1.043 GB/1.566 GB
a13e6b26f7d9: Download complete
6ea9c263f713: Download complete

C:\test\QuantumAPI\QuantumAPI>docker pull microsoft/dotnet-framework:4.6.2-runtime
4.6.2-runtime: Pulling from microsoft/dotnet-framework
3889bb8d808b: Already exists
d0c71fc8924e: Extracting [=================================>                 ] 1.041 GB/1.566 GB
a13e6b26f7d9: Download complete
6ea9c263f713: Download complete

Always gets stuck at extracting

C:\test\QuantumAPI\QuantumAPI>docker version
Client:
 Version:      1.12.2-cs2-ws-beta
 API version:  1.25
 Go version:   go1.7.1
 Git commit:   050b611
 Built:        Tue Oct 11 02:35:40 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.2-cs2-ws-beta
 API version:  1.25
 Go version:   go1.7.1
 Git commit:   050b611
 Built:        Tue Oct 11 02:35:40 2016
 OS/Arch:      windows/amd64

@octocat-mona
Copy link

/remove-lifecycle stale

@octocat-mona
Copy link

Same issue here on Windows Server 2019

@SpyRefused
Copy link

Same issue on Windows Server 2019 too.

@Celludriel
Copy link

Same issue Windows 7 Enterprise 64-bit (6.1, Build 7601)

@jigar-dhulla
Copy link

jigar-dhulla commented Mar 16, 2019

https://stackoverflow.com/questions/50530262/docker-daemon-windows-7-concurrent-downloads

Passing extra argument --max-concurrent-downloads to 1 fixed the issue for me.

@Celludriel
Copy link

While I wouldn't call this a fix, it's a good workaround for those of us in trouble. Thanks for teaching this !

@RKopczynski
Copy link

Problem still exists. I have quite fresh installation of windows.
OS Name: Microsoft Windows 10 Education (64bit EN)
Version: 10.0.17763 Build 17763

Installed docker today to run Gitlab CI/CD runner, cannot pull a single image.

@btodts
Copy link

btodts commented Apr 16, 2019

For what it's worth: I only had this issue when using windows containers. Switching to linux containers (and pulling linux images) works fine.

I managed to pull images for windows by running the Docker Daemon in elevated mode - although it took at least 20 minutes to pull the image (in my case, microsoft/mssql-server-windows-developer).

@johnmccain
Copy link

johnmccain commented May 20, 2019

I have had this issue when pulling Linux containers as well (jupyter/pyspark-notebook for one).

I am also seeing the same error as other users in the logs: vpnkit.exe: PPP.listen callback caught (Invalid_argument

Sometimes the pull fails silently, but often I get this message which coincides with the vpnkit error in the logs.

error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/1e/1e5b702d2dd410c2776c556d13ab9e2bc0f1ee831a881a8d6f41be34367b792b/data?verify=1558365041-y8%2Bd6OtQUh0SzD7WNzCd8Ol%2B1L8%3D: local error: tls: bad record MAC

I am running the latest version of Docker for Windows.

Logs:

[09:09:39.187][ApiProxy       ][Info   ] Dial Hyper-V socket 4a7218ad-47df-4641-8b15-a8436b32f095:23a432c2-537a-4291-bcb5-d62504644739
[09:09:39.188][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 4a7218ad-47df-4641-8b15-a8436b32f095:23a432c2-537a-4291-bcb5-d62504644739
[09:09:39.193][ApiProxy       ][Info   ] proxy << GET /v1.27/info
[09:09:39.253][ApiProxy       ][Info   ] proxy >> POST /v1.27/images/create?fromImage=jupyter%2Fpyspark-notebook&tag=latest
[09:09:39.253][ApiProxy       ][Info   ] Dial Hyper-V socket 4a7218ad-47df-4641-8b15-a8436b32f095:23a432c2-537a-4291-bcb5-d62504644739
[09:09:39.253][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 4a7218ad-47df-4641-8b15-a8436b32f095:23a432c2-537a-4291-bcb5-d62504644739
[09:09:41.547][VpnKit         ][Error  ] vpnkit.exe: PPP.listen callback caught (Invalid_argument
[09:09:41.548][VpnKit         ][Info   ]   "Cstruct.blit src=[7753,1380](65536) dst=[0,4096](4096) dst-off=2814 len=1380")
[09:12:53.087][VpnKit         ][Error  ] vpnkit.exe: PPP.listen callback caught (Invalid_argument
[09:12:53.087][VpnKit         ][Info   ]   "Cstruct.blit src=[7737,1380](65536) dst=[0,4096](4096) dst-off=2796 len=1380")

@jpruiz114
Copy link

jpruiz114 commented Jun 8, 2019

Leaving a comment here since this is happening to me as well.

On an additional note, seems like restarting the daemon helps:
sudo service docker restart

Still, restarting the daemon shouldn't be needed.

@std4453
Copy link

std4453 commented Jun 26, 2019

In our environment, downloading a certain layer (200+MB) ALWAYS stuck at about 100MB progress and docker pull freezes forever. I'd hope that docker allows something like "continue downloading" after I manually ctrl-c to stop docker pull.

@rdx-daniel-oliveira
Copy link

Same here:

C:\Windows\system32>docker pull microsoft/dotnet-framework:4.6.2-runtime-windowsservercore-ltsc2016
4.6.2-runtime-windowsservercore-ltsc2016: Pulling from microsoft/dotnet-framework
3889bb8d808b: Downloading [=====================> ] 1.727GB/4.07GB
c0f6863f3dd4: Download complete
fb72e3c6589b: Download complete
65e1c033c2eb: Download complete

Report Id: 61D96729-F48C-4746-8036-A3DE264B6608/20181018110138
OS: Windows 10
Docker version: 18.06.1-ce

Same issue and same image

@udpnarola
Copy link

Facing the same issue while pulling the docker image it stuck all the time, please fix this problem. It's very annoying.

@tineo
Copy link

tineo commented Feb 24, 2020

I'm the same problen on Win10. I can't pulling nothing.

@udpnarola
Copy link

udpnarola commented Feb 25, 2020

@tineo I found a way to solve this problem, apply the following changes.

  1. Right-click on the tiny icon of the Docker from the taskbar
  2. Click on settings
  3. Click on "Docker Engine" from the left side panel
  4. add this line in the existing JSON ("max-concurrent-downloads": 1)
  5. The JSON should look like this
    {
    "registry-mirrors": [],
    "insecure-registries": [],
    "debug": true,
    "experimental": false,
    "max-concurrent-downloads": 1
    }
  6. Restart the Docker and problem solved.

This will initialize only one download at a time.

Note: These steps are for Docker App, not for Docker ToolBox

@tineo
Copy link

tineo commented Feb 25, 2020

/remove-lifecycle stale

@kkn4
Copy link

kkn4 commented Feb 25, 2020

Setting "max-concurrent-downloads" to 1, didn't resolve the issue on a windows 10 pro machine. Followed @MatthewLymer 's advice and kept killing the vpnkit.exe so that the process would "restart" download and complete eventually!

@tineo
Copy link

tineo commented Feb 25, 2020

@kkn4 Setting "max-concurrent-downloads" to 1. Works for me on a Win 10 Pro.

@mike7ang1rdz
Copy link

Leaving a comment here since this is happening to me as well.

On an additional note, seems like restarting the daemon helps:
sudo service docker restart

Still, restarting the daemon shouldn't be needed.

agreed... a retry/timeout mechanisim and saved chunks should be implemented

@davidcblaney
Copy link

davidcblaney commented Mar 4, 2020

I experienced this issue when using Docker for Windows on Windows 7.

My host machine running out of memory and pausing the docker machine. I assume this behaviour enforced by Virtualbox to prevent the host running out of memory.

Server Version: 18.06.1-ce
...
Kernel Version: 4.9.93-boot2docker
Operating System: Boot2Docker 18.06.1-ce (TCL 8.2.1); HEAD : c7e5c3e - Wed Aug 22 16:27:42 UTC 2018
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.858GiB
...
Labels:
provider=virtualbox

@BillGatesPriv
Copy link

I had the same error and installing Golang and adding it to the $PATH variable in the /etc/profile fixed it for me. Hope that helps someone.

@docker-robott
Copy link
Collaborator

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

@howion
Copy link

howion commented Jul 5, 2020

/remove-lifecycle stale

@docker-robott
Copy link
Collaborator

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

@bukowa
Copy link

bukowa commented Oct 27, 2020

/remove-lifecycle stale

@Fredsters
Copy link

Still happens to me, I tried all the suggestions here, for now without success. On Windows 10.
Each time I pull it stops somewhere else in the download progress. Sometimes very early. Sometimes short before finished. The download time is usually only a few seconds.

@bukowa
Copy link

bukowa commented Dec 1, 2020

/lifecycle frozen

@AdityaNikhil
Copy link

AdityaNikhil commented Dec 14, 2020

🔥🔥🔥🔥🔥🔥🔥🔥🔥

Well... I've almost tried all the solutions mentioned above. What finally worked for me is,

I have quit the vpnkit.exe from task manager as suggested by @MatthewLymer .
BUT STILL IT DIDN'T WORK,

UNTIL

I pressed up arrow key on my keyboard.

🎉🎉🎉🎉🎉🎉That finally finished the downloads. Hope it helps! 🎉🎉🎉🎉🎉🎉

@Luca-Terrazzan
Copy link

🔥🔥🔥🔥🔥🔥🔥🔥🔥

Well... I've almost tried all the solutions mentioned above. What finally worked for me is,

I have quit the vpnkit.exe from task manager as suggested by @MatthewLymer .
BUT STILL IT DIDN'T WORK,

UNTIL

I pressed up arrow key on my keyboard.

🎉🎉🎉🎉🎉🎉That finally finished the downloads. Hope it helps! 🎉🎉🎉🎉🎉🎉

I cannot believe this worked but it did

@harveydobson
Copy link

I had this issue on mac and was able to pin it down to switching my antivirus over to Kaspersky some weeks back. If you pause protection, it works just fine.

@cyrionp
Copy link

cyrionp commented Sep 19, 2022

🔥🔥🔥🔥🔥🔥🔥🔥🔥

Well... I've almost tried all the solutions mentioned above. What finally worked for me is,

I have quit the vpnkit.exe from task manager as suggested by @MatthewLymer . BUT STILL IT DIDN'T WORK,

UNTIL

I pressed up arrow key on my keyboard.

🎉🎉🎉🎉🎉🎉That finally finished the downloads. Hope it helps! 🎉🎉🎉🎉🎉🎉

The problem still happens and this unexpected solution is still working 😄🥇

@MatthewLymer
Copy link

It's docker's Konami code.

@maisiejillbt
Copy link

I'm on an M1 mac and none of this worked for me!!!

What fixed it was resetting my Github SSH key!

Why did this work? I don't know and I don't care, hope it helps someone else! I followed the Github guide's here -

  1. https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
  2. https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account

@OSK-tspees
Copy link

I'm on an M1 mac and none of this worked for me!!!

What fixed it was resetting my Github SSH key!

Why did this work? I don't know and I don't care, hope it helps someone else! I followed the Github guide's here -

  1. https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
  2. https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account

I'm on Linux Mint and regenerating ssh keys worked for me.

I tested all other options (Reinstall docker, run dockerd with concurrent-downloads == 1, restart docker mid download, press up arrow) and none of them had any impact.

@faulker
Copy link

faulker commented Jun 21, 2023

I know this is a Windows thread but my searching brought me here and figured I'd note that on OSX 13.4 Docker v24.0.2 with BuildKit disabled (because that was causing other image download issues) I was having the same issue and setting max-concurrent-downloads to 1 fixed it for me but not a great solution IMHO

@salouri
Copy link

salouri commented Sep 7, 2023

I am on my windows 10 Pro and I am using docker over WSL2. I couldn't find vpnkit.exe file or process. I found out that my docker is pending an update to version 4.22.1 so once I downloaded and installed the update "docker pull" command started working again!
I guess it was the re-install process that was initiated as part of the update operation that fixed it for me. So, if you can't find vpnkit.exe file, just update/reinstall you docker. Hope that helps someone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests