search

docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.43k stars 117 forks source link

docker pull hangs downloading image #2083

Closed sebastianperruolo closed 2 years ago

sebastianperruolo commented 7 years ago

I tried several times to pull mssql-server-linux but I got always the same result.

$ docker pull microsoft/mssql-server-linux
latest: Pulling from microsoft/mssql-server-linux
aed15891ba52: Already exists 
773ae8583d14: Already exists 
d1d48771f782: Already exists 
cd3d6cd6c0cf: Already exists 
8ff6f8a9120c: Already exists 
1fd7e8b10447: Already exists 
bd485157db89: Already exists 
273a1970ce9c: Already exists 
c6f0182f94e9: Downloading [=================================================> ]  275.2MB/275.7MB
47c608bf53ae: Waiting

Expected behavior

Finish dowloading of mssql-server-linux image

Actual behavior

It always hang with the same fs file with id c6f0182f94e9

Information

Docker for Mac: version: 17.06.2-ce-mac27 (4cdec4294a50b2233146b09469b49937dabdebdd) macOS: version 10.12.6 (build: 16G29) logs: /tmp/5542512B-8253-4454-9064-2CD6AD31D520/20170922-191740.tar.gz [OK] db.git [OK] vmnetd [OK] dns [OK] driver.amd64-linux [OK] virtualization VT-X [OK] app [OK] moby [OK] system [OK] moby-syslog [OK] db [OK] env [OK] virtualization kern.hv_support [OK] slirp [OK] osxfs [OK] moby-console [OK] logs [OK] docker-cli [OK] menubar [OK] disk

Steps to reproduce the behavior

  1. Run docker pull microsoft/mssql-server-linux
  2. Wait
dzmitry-kankalovich commented 3 years ago

Had the same problem with the postgres image recently. Not sure of the root cause, but limiting concurrent connections to 1 helped:

{
  "max-concurrent-downloads": 1 
}
ingomueller-net commented 3 years ago

Very curious... I am experiencing the same problem using Amazon Linux in EC2 (and a different image). Interestingly, the download progress is not zero; it is just very slow. The most curious thing is that, after trying with a different instance, the download was fast until the point that the first instance has reached and become slow after that. It looks like some server in the docker hub (?) or a cache layer in between (?) is slowing down the download of this specific layer...

SmetDenis commented 3 years ago

I have the same issue :( Any thoughts on this moment?

Reeebuuk commented 3 years ago

Had same issue. Restarting docker machine didn't help but restarting whole mac resolved the issue for some reason :/ Setting max-concurrent-downloads didn't help.

Niek commented 3 years ago

Same issue here, it seems to happen on specific layers. Changing max-concurrent-downloads didn't help for me.

daylioti commented 3 years ago

Same issue, windows WSL2 for bitnami/solr:8

https://hub.docker.com/layers/bitnami/solr/8/images/sha256-07a87e23eb611a9827a6e362948d8136b54faa748eda39a169d633f9861263b9?context=explore

stuck (very very slow download) on layer "/bin/sh -c /opt/bitnami/scripts/solr/postunpack.sh"

max-concurrent-downloads, restarts not helps

Hasanabbas commented 3 years ago

How is this issue still not fixed after 4 years?!

raohammad commented 3 years ago

I have this issue even today and its with almost all images that I try to pull. To handle it, I have to terminate (ctrl+c) and restart. Sometimes it takes multiple times to get a successful pull. Each time it hangs at different progress level

harveydobson commented 2 years ago

So I've had this issue for the past few weeks and just today realised the cause was switching to Kaspersky Antivirus. If I pause the protection, there is no interruption to my downloads.

So I'm happy - I just wish I had found that out before destroying my entire docker environment... which by the way if you were looking to do, this is a very good guide for mac https://www.mytecbits.com/apple/macos/clean-way-to-uninstall-docker

chris-metz commented 2 years ago

Having the same issue on 2 local machines (Windows w/ WSL2 and macos respectively). On both machines when pulling images it starts quiet fast and then slows down to an almost zero speed.

However, pulling images on a VPS works fast without any problems.

salesfelipe commented 2 years ago

I was having this same issue on my local machine (MAC OSX). It was solved when I closed the Kapersky application and restarted the docker app as explained above. My guess is that Kaspersky, which is an anti-virus/endpoint protection application was blocking the docker requests. Turning off these applications is worth a shot! Good luck :)

egor-ryashin commented 2 years ago

I think at this point Kaspersky ought to fix its bugs, so many people turn it off to be able to work.

oharkins commented 2 years ago

March 16, 2022

Same Issue Still Happening

johnib commented 2 years ago

For me it happened on streams that were interrupted when I cancelled the pull with ctrl+c and then executed it again. Not sure what can be done to recover from this state.. it seems like consequtive pulls do not start downloading from scratch, but from where the stream was intrrupted.

Emememssss commented 2 years ago

did anyone resolved this?

oharkins commented 2 years ago

Based on the fact that mine just eventually finished I think the process would need to be killed I just looked later and they had finished even tho I ctrl+c out of the process.

Emememssss commented 2 years ago

okay thanks. I also resolved it by halting the process, then restarting the laptop/ or would be the vm in other cases.

On Sat, Mar 26, 2022 at 4:45 AM Odis Harkins @.***> wrote:

Based on the fact that mine just eventually finished I think the process would need to be killed I just looked later and they had finished even tho I ctrl+c out of the process.

— Reply to this email directly, view it on GitHub https://github.com/docker/for-mac/issues/2083#issuecomment-1079421016, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARVIX3Q5FAH6GYU7DR5YWODVBYQU7ANCNFSM4D4FHOEA . You are receiving this because you commented.Message ID: @.***>

mervanerdem commented 2 years ago

systemctl restart docker in ubuntu worked for me

JuanFontes commented 2 years ago

Restarting docker worked for me.

image
ibrt commented 2 years ago

Issue is real and it's quite bizarre that it still exists many years after being first reported. One thing I noticed is that it might be network-dependent, i.e. it never happened to me until I started working at a coworking space which uses https://www.nuvisions.net as provider. Connection is actually pretty solid, never experienced other problems. But this issue now happens to me consistently, only on this network.

akhilesh84 commented 2 years ago

Restarting docker worked for me.

image

For me too...

NedislavKolev commented 2 years ago

I had the same problem with Docker on Windows with WSL restarting it fixed the issue.

DamonOnYT commented 2 years ago

Having this same issue on Ubuntu. Restarting didn't help

wuduanq commented 2 years ago

same issue in ubuntu vm, for 6 years

wuduanq commented 2 years ago

it's time to close the issue

slavanorm commented 2 years ago

its funny that i have "stuck" progress visually, but then it turned out that it just turns to "Download Complete" without updating the progress numbers

HeikoNardmann commented 2 years ago

I have the same issue inside a Win11 VirtualBox VM. Even with "max-concurrent-downloads" set to 1 it does not help. I get the error message "unknown blob". And the layers downloaded last time are re-downloaded once again ... which is annoying even more: the whole process stops with that error message which even kills the currently running "Extracting" of another layer.

najb121 commented 2 years ago

I was facing the same issue but after hitting Ctrl-C the download seemed to resume

eben0 commented 2 years ago

Pruning all build cache worked for me:

docker builder prune -a

maisiejillbt commented 2 years ago

What fixed this on my M1 mac was resetting my Github SSH key!

Hope it helps someone else! I followed the Github guide's here -

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

nicks commented 2 years ago

Hi all - I'm going to close this issue. The original reporter said that the problem was fixed for them. Since then, the issue has become a dumping ground for random unrelated pull problems -- possibly caused by faulty networks, faulty anti-virus software, or misunderstandings about registry auth.

If you believe there's a bug that persists for you, please file a new issue with detailed repro steps and/or diagnostics. This allows us to track and fix problems more effectively. Thanks!

docker-robott commented 2 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