Docker pull fails often

Hi,

we’re using Docker images from the Docker hub to run integration tests against in our php tests. Since a few weeks the pull regularly shows

docker pull catatnight/postfix

Using default tag: latest

Error response from daemon: unexpected EOF

https://travis-ci.com/nextcloud/mail/jobs/284838321

It looks like this could be a timeout issue. Is there any rate limiting active for network traffic coming from Travis, maybe? Restarting the job helps sometimes, but certainly not always.

I also tried deleting all caches. Same result with a fresh setup.

Cheers

I get timeouts on my home machine, so I tend to think the issue is more widespread than just our network.

$ for in in $(seq 1 10); do docker pull catatnight/postfix; done
Using default tag: latest
Error response from daemon: unexpected EOF
Using default tag: latest
Error response from daemon: unexpected EOF
Using default tag: latest
Error response from daemon: unexpected EOF
Using default tag: latest
Error response from daemon: unexpected EOF
Using default tag: latest
latest: Pulling from catatnight/postfix
Image docker.io/catatnight/postfix:latest uses outdated schema1 manifest format. Please upgrade to a schema2 image for better future compatibility. More information at https://docs.docker.com/registry/spec/deprecated-schema-v1/
a3ed95caeb02: Pull complete
bb92073c7a94: Pull complete
255c0b817d4e: Pull complete
b5111d9274a4: Pull complete
2b5c23db3bbc: Pull complete
1fb9bd8e91f3: Pull complete
1775fca35fb6: Pull complete
704b646b3521: Pull complete
7a69bc1c1265: Pull complete
2688108bfd48: Pull complete
Digest: sha256:11684ea62492d31bd65d4f184c6cc02519d00b4b571ea1df8e363ac5e4ee028c
Status: Downloaded newer image for catatnight/postfix:latest
docker.io/catatnight/postfix:latest
Using default tag: latest
Error response from daemon: unexpected EOF
Using default tag: latest
Error response from daemon: unexpected EOF
Using default tag: latest
latest: Pulling from catatnight/postfix
Image docker.io/catatnight/postfix:latest uses outdated schema1 manifest format. Please upgrade to a schema2 image for better future compatibility. More information at https://docs.docker.com/registry/spec/deprecated-schema-v1/
a3ed95caeb02: Already exists
bb92073c7a94: Already exists
255c0b817d4e: Already exists
b5111d9274a4: Already exists
2b5c23db3bbc: Already exists
1fb9bd8e91f3: Already exists
1775fca35fb6: Already exists
704b646b3521: Already exists
7a69bc1c1265: Already exists
2688108bfd48: Already exists
Digest: sha256:11684ea62492d31bd65d4f184c6cc02519d00b4b571ea1df8e363ac5e4ee028c
Status: Image is up to date for catatnight/postfix:latest
docker.io/catatnight/postfix:latest
Using default tag: latest
latest: Pulling from catatnight/postfix
Image docker.io/catatnight/postfix:latest uses outdated schema1 manifest format. Please upgrade to a schema2 image for better future compatibility. More information at https://docs.docker.com/registry/spec/deprecated-schema-v1/
a3ed95caeb02: Already exists
bb92073c7a94: Already exists
255c0b817d4e: Already exists
b5111d9274a4: Already exists
2b5c23db3bbc: Already exists
1fb9bd8e91f3: Already exists
1775fca35fb6: Already exists
704b646b3521: Already exists
7a69bc1c1265: Already exists
2688108bfd48: Already exists
Digest: sha256:11684ea62492d31bd65d4f184c6cc02519d00b4b571ea1df8e363ac5e4ee028c
Status: Image is up to date for catatnight/postfix:latest
docker.io/catatnight/postfix:latest
Using default tag: latest
Error response from daemon: unexpected EOF
1 Like

You’re right. It’s reproducible here as well. Not very often, but sometimes. Guess my connection is slightly better than the one in the build jobs.

I’ll see if I can report this at Docker.

Cheers

Imprint