Docker pull hangs - never calls callback

[kyleburnett]

I'm using dockerode to pull down images from a private repository. Occasionally - maybe about 10% of the time - dockerode hangs because the modem never calls the callback with the stream. After putting some logging messages into lib/modem.js in the docker-modem dependency, I discovered that a typical pull causes 2 json responses (line 232 of modem.js) followed by a stream response (line 230 of modem.js). When the modem hangs, I don't see a stream response. Tailing the registry logs, I don't see anything out of the ordinary; it looks the same from a successful pull to an unsuccessful one.

I'm not sure if this is an issue with dockerode, docker-modem, docker daemon, or the registry. Is there a good way to find out?

[kyleburnett]

So it appears docker pull hangs only because the i/o timeout was longer than the test timeout that I was running. Looking at the docker logs, this is the error:

ERRO[10608] Error from V2 registry: Get https://registry.thinknode.dev/v2/035088a9398b/math/manifests/sha256:10af39c70b7b7f3bc6d9539c38180d67a626c033487e706e5396d3c5af6c58a8: read tcp 127.0.0.1:443: i/o timeout 
ERRO[10608] Handler for POST /images/create returned error: pulling with digest reference failed from v2 registry 
ERRO[10608] HTTP Error                                    err=pulling with digest reference failed from v2 registry statusCode=500

[kyleburnett]

This seems to be related to moby/moby#13337 and not at all related to dockerode. Closing.