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

Docker pull fails with unexpected EOF in archive #2461

Closed
tgummerer opened this Issue Oct 30, 2013 · 90 comments

Comments

Projects
None yet
@tgummerer
Copy link

tgummerer commented Oct 30, 2013

Hi,

I've started to try out docker, but can't pull large images. docker pull busybox for example works fine, while docker pull centos or docker pull ubuntu give me an error similar to the following:

core@localhost ~ $ docker pull centos
Pulling repository centos
539c0211cd76: Error pulling image (latest) from centos, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
539c0211cd76: Error pulling image (latest) from centos, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
2013/10/30 11:31:57 Server error: 404 trying to fetch remote history for centos

The daemon gives the followinng output when debug is turned on, in case it's helpful:

[debug] api.go:962 Calling POST /images/create
2013/10/30 11:35:06 POST /v1.6/images/create?fromImage=centos&tag=
[debug] registry.go:294 [registry] Calling GET https://index.docker.io/v1/repositories/centos/images
[debug] server.go:478 Retrieving the tag list
[debug] registry.go:269 Got status code 200 from https://cdn-registry-1.docker.io/v1/repositories/library/centos/tags
[debug] server.go:493 Registering tags
[debug] registry.go:179 Ancestry: [
    "539c0211cd76cdeaedbecf9f023ef774612e331137ce7ebe4ae1b61088e7edbe"
]
[debug] image.go:338 Json string: {{"comment": "Imported from -", "container_config": {"Tty": false, "Cmd": null, "MemorySwap": 0, "Image": "", "Hostname": "", "User": "", "Env": null, "Memory": 0, "Detach": false, "Ports": null, "OpenStdin": false}, "id": "539c0211cd76cdeaedbecf9f023ef774612e331137ce7ebe4ae1b61088e7edbe", "created": "2013-04-01T01:20:58.331937915-07:00"}}

[debug] image.go:91 Start untar layer
[debug] archive.go:119 [tar autodetect] n: 10
[debug] archive.go:124 Archive compression detected: tar.gz
core@localhost ~ $ docker version
Client version: 0.6.4
Go version (client): go1.1.2
Git commit (client): e8da766
Server version: 0.6.4
Git commit (server): e8da766
Go version (server): go1.1.2
Last stable version: 0.6.4

I'm running CoreOS under vagrant.

@jpetazzo

This comment has been minimized.

Copy link
Contributor

jpetazzo commented Oct 30, 2013

Which version of tar are you using?
(I wonder if this might be an issue related to CoreOS?)

@tgummerer

This comment has been minimized.

Copy link

tgummerer commented Oct 30, 2013

core@localhost ~ $ tar --version
tar (GNU tar) 1.26
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.

Oh and I forgot to mention, it starts downloading stuff, and then the error pops up. Mostly it stops when only a few megabytes (1-5) were downloaded, but other times (less common) it manages to download 50-70 MB.

@jpetazzo

This comment has been minimized.

Copy link
Contributor

jpetazzo commented Oct 31, 2013

Ah, in that case, I'm willing to place on bet on odd network conditions :-)
How is the machine connected to the network?
Since you mentioned CoreOS under vagrant, I suppose that this is running on
your local machine.
Can you connect to a different network and see if it behaves the same?
Are you able to download big-ish files? (e.g. an Ubuntu ISO image)

On Wed, Oct 30, 2013 at 8:29 AM, Thomas Gummerer
notifications@github.comwrote:

core@localhost ~ $ tar --version
tar (GNU tar) 1.26
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.

Oh and I forgot to mention, it starts downloading stuff, and then the
error pops up. Mostly it stops when only a few megabytes (1-5) were
downloaded, but other times (less common) it manages to download 50-70 MB.


Reply to this email directly or view it on GitHubhttps://github.com//issues/2461#issuecomment-27399522
.

@tgummerer

This comment has been minimized.

Copy link

tgummerer commented Oct 31, 2013

Yeah you're right, the problem was more the wifi card than the actual network it seems, but that comes down to the same thing ;-) Sorry for the noise.
Downloading big files is possible, but only because wget handles read error and continues to download afterwards. Might that be something worth implementing in docker?

@tgummerer tgummerer closed this Oct 31, 2013

@tavisrudd

This comment has been minimized.

Copy link

tavisrudd commented Nov 4, 2013

I've run into this on multiple machines/networks when downloading tianon/gentoo. It fails the first time then succeeds on second run. Most recently was on Joyent, who have a fairly reliable network. "1c8fbfa2ee2d: Error pulling image (stage3-20130516) from tianon/gentoo, exit status 2: tar: Unexpected EOF in archive"

@jpetazzo

This comment has been minimized.

Copy link
Contributor

jpetazzo commented Nov 4, 2013

I'm reopening.

@samalba do you know if there is an easy way to bypass the CDN (to check if that might be the CDN's fault)?

@jpetazzo jpetazzo reopened this Nov 4, 2013

@tavisrudd

This comment has been minimized.

Copy link

tavisrudd commented Nov 8, 2013

Another data point: I ran into this again the first time I tried to pull from a digitalocean vm. Re-running it immediately resolved the issue as it had previously.

@gmbuell

This comment has been minimized.

Copy link

gmbuell commented Nov 13, 2013

I'm seeing the same problem on a vagrant virtualbox image. Fails the first time, succeeds the second.

@jvermillard

This comment has been minimized.

Copy link

jvermillard commented Nov 21, 2013

Same problem here, 3 tries before success:

core@localhost ~ $ docker pull centos                                                                                                                                                                                                                                                                                        
Pulling repository centos
539c0211cd76: Error pulling image (latest) from centos, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
539c0211cd76: Error pulling image (latest) from centos, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
2013/11/21 10:33:33 Server error: 404 trying to fetch remote history for centos
core@localhost ~ $ docker pull centos                                                                                                                                                                                                                                                                                        
Pulling repository centos
539c0211cd76: Error pulling image (latest) from centos, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
539c0211cd76: Error pulling image (latest) from centos, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
2013/11/21 11:06:38 Server error: 404 trying to fetch remote history for centos
core@localhost ~ $ docker pull centos                                                                                                                                                                                                                                                                                        
Pulling repository centos
539c0211cd76: Download complete
@samalba

This comment has been minimized.

Copy link
Contributor

samalba commented Nov 21, 2013

Thanks for the data. Could you give some details on how long does it take when it fails? Does it fail right away or is there some kind of timeout?

@jvermillard

This comment has been minimized.

Copy link

jvermillard commented Nov 22, 2013

dunno exactly but looks like some kind of timeout when the download is stuck.
For example I have a lot of trouble to download this image: kimh/oracledb (~1.3GB)

@rogaha

This comment has been minimized.

Copy link
Contributor

rogaha commented Nov 28, 2013

Currently the cookie session lasts only one hour. If the downloading process takes more that one hour you should get the error 404 after that period of time.

@samalba, do you think that we could increase the expiration period?

@tianon

This comment has been minimized.

Copy link
Member

tianon commented Nov 28, 2013

Is there a particular reason why we can't just use a session cookie?

@samalba

This comment has been minimized.

Copy link
Contributor

samalba commented Nov 28, 2013

@tianon do you mean a cookie without expires? If yes, I we can.

@tianon

This comment has been minimized.

Copy link
Member

tianon commented Nov 30, 2013

Yes, that's exactly what I mean. Then we can take as long as we need to. :)

@justcookin

This comment has been minimized.

Copy link

justcookin commented Dec 6, 2013

Kept on getting this on several pull requests:

$sudo docker pull  inokappa/squeeze-basic 
Pulling repository inokappa/squeeze-basic
050462b16e32: Error pulling image (latest) from inokappa/squeeze-basic, endpoint: https://cdn-registry-    1.docker.io/v1/, exit status 2: 
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
050462b16e32: Error pulling image (latest) from inokappa/squeeze-basic, exit status 2: Error is not recoverable: exiting now
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
2013/12/06 15:23:02 Server error: 404 trying to fetch remote history for inokappa/squeeze-basic

Had to run it 2 times for this particular repository, second time it worked fine. Running docker on an Amazon EC2 ubuntu instance.

@samalba

This comment has been minimized.

Copy link
Contributor

samalba commented Dec 7, 2013

We pushed a fix candidate on prod this week on the public Registry. Can anyone update the status on this? The problem is supposed to be solved.

Reference: docker/docker-registry@e5d96a1

@rogaha

This comment has been minimized.

Copy link
Contributor

rogaha commented Dec 7, 2013

I was trying to replicate that problem and I couldn't do it any more. Hopefully it should be fixed with that fix candidate.

@albertogg

This comment has been minimized.

Copy link

albertogg commented Dec 13, 2013

I know this has been discussed several times... I'm always getting stuck while downloading the "ubuntu" image. My problem is that it keeps throwing the Unexpected EOF in archive error while been at 3.342 MB/94.86 MB 52m1s this has happened every single time for the past 6 tries. I'm running Docker within Vagrant within VirtualBox, with a bridged network.

$ docker pull ubuntu
Pulling repository ubuntu
8dbd9e392a96: Error pulling image (precise) from ubuntu, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'
xz: (stdin): Unexpected end of input                                          ] 3.342 MB/94.86 MB 52m1s
8dbd9e392a96: Error pulling image (precise) from ubuntu, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'ed EOF in archive
xz: (stdin): Unexpected end of inputng now
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

The software versions.

$ docker version
Client version: 0.7.1
Go version (client): go1.2
Git commit (client): 88df052
Server version: 0.7.1
Git commit (server): 88df052
Go version (server): go1.2
Last stable version: 0.7.1

$ tar --version
tar (GNU tar) 1.26

$ vagrant -v
Vagrant 1.4.0

VirtualBox 4.3.4 with its guest additions.

Its really weird that it always breaks in the same part... also I'm not getting the 404 error, I have to interrupt the execution and and kill the docker process to be availed to retry the docker pull ubuntu.

Update: now I'm getting this.

$ docker pull ubuntu
Pulling repository ubuntu
8dbd9e392a96: Downloading [====>                                              ] 5.014 MB/58.34 MB 29m12s
b750fe79269d: Error pulling image (quantal) from ubuntu, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2:
gzip: stdin: unexpected end of fileendent layers
tar: Unexpected EOF in archive
b750fe79269d: Error pulling image (quantal) from ubuntu, exit status 2:
gzip: stdin: unexpected end of fileing now
8dbd9e392a96: Error pulling image (precise) from ubuntu, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
xz: (stdin): Unexpected end of input
8dbd9e392a96: Error pulling image (precise) from ubuntu, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'ed EOF in archive
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
xz: (stdin): Unexpected end of input
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
2013/12/13 19:49:33 Could not find repository on any of the indexed registries.
@mait

This comment has been minimized.

Copy link

mait commented Dec 25, 2013

➜ ~ sudo docker pull coreos/etcd
Pulling repository coreos/etcd
ff181fe39317: Error pulling image (latest) from coreos/etcd, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'ading dependent layers
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
xz: (stdin): Unexpected end of input
tar: Unexpected EOF in archive
ff181fe39317: Error pulling image (latest) from coreos/etcd, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
xz: (stdin): Unexpected end of input
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
2013/12/25 17:34:43 Could not find repository on any of the indexed registries.

samsaffron/discourse, coreos/etcd failed.

busybox OK.

Now I'm trying ubuntu. It looks like working. In progress.

Uubuntu 13.10

Client version: 0.7.2
Go version (client): go1.2
Git commit (client): 28b162e
Server version: 0.7.2
Git commit (server): 28b162e
Go version (server): go1.2
Last stable version: 0.7.2

tar (GNU tar) 1.26
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.
@mait

This comment has been minimized.

Copy link

mait commented Dec 25, 2013

docker pull ubuntu started at 18:00. Now 22:50. Still 60MB/94MB in progress.

South Korea banned from CDN? I'm wondering why this is so slow.

@albertogg

This comment has been minimized.

Copy link

albertogg commented Dec 25, 2013

@mait it's stuck and it will not continue, that happens to me also... when it doesn't break with the tar: Unexpected EOF in archive

@dinogun

This comment has been minimized.

Copy link

dinogun commented Jan 13, 2014

$ sudo docker pull ubuntu
2014/01/13 12:47:43 POST /v1.8/images/create?fromImage=ubuntu&tag=
Pulling repository ubuntu
8dbd9e392a96: Downloading [==========> ] 11.7 MB/58.34 MB 12m24s
b750fe79269d: Error pulling image (quantal) from ubuntu, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
b750fe79269d: Error pulling image (quantal) from ubuntu, exit status 2: tar: Ignoring unknown extended header keyword `SCHILY.fflags'

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
8dbd9e392a96: Download complete
tar: Error is not recoverable: exiting now

2014/01/13 13:03:39 Could not find repository on any of the indexed registries.

This is from Bangalore, India

@porterjamesj

This comment has been minimized.

Copy link

porterjamesj commented Jan 16, 2014

I am also seeing this from inside of a private cloud:

$ docker pull chapmanb/bcbio-nextgen-vm
Pulling repository chapmanb/bcbio-nextgen-vm
2014/01/15 22:49:37 HTTP code: 404
ubuntu@docker-test:/usr/local/Cellar/samtools/0.1.19/share/man/man1$ sudo docker pull chapmanb/bcbio-nextgen-devel
Pulling repository chapmanb/bcbio-nextgen-devel
d6c738103f22: Error pulling image (latest) from chapmanb/bcbio-nextgen-devel, endpoint: https://cdn-registry-1.docker.io/v1/, exit status 2:
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archivee
tar: Unexpected EOF in archivee
tar: Error is not recoverable: exiting nowlayers
d6c738103f22: Error pulling image (latest) from chapmanb/bcbio-nextgen-devel, exit status 2:
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now





2014/01/15 22:54:48 Could not find repository on any of the indexed registries.

and as others have reported; it works fine on the second try.

@narkisr

This comment has been minimized.

Copy link

narkisr commented Jan 16, 2014

I can confirm this happening also

@samalba

This comment has been minimized.

Copy link
Contributor

samalba commented Jan 16, 2014

I was able to reproduce a couple of times. It looks like while Docker is fetching layers from CloudFlare, the connection gets interrupted sometimes.

We're currently implementing bytes-range support on the Registry, so we'll be able to transparently retry on fail (and not have to restart from scratch).

I am assigning this to me, to coordinate.

@ghost ghost assigned samalba Jan 16, 2014

@unclejack

This comment has been minimized.

Copy link
Contributor

unclejack commented May 27, 2014

@crquan You can send a PR and we can discuss on the PR, even if it's not ready. However, you should keep the resume code out of the PR which adds support for timeouts.

@crquan

This comment has been minimized.

Copy link
Contributor

crquan commented May 27, 2014

@unclejack got it, create #6048

crquan added a commit to crquan/docker that referenced this issue May 28, 2014

Create temporary file to save partial download file and resume downlo…
…ading

This fixed 2nd part of moby#6024, or moby#2461

Docker-DCO-1.1-Signed-off-by: Derek <crq@kernel.org> (github: crquan)
@davidpelaez

This comment has been minimized.

Copy link
Contributor

davidpelaez commented Jun 1, 2014

I continue to experience this issue under Fedora 20 regardless of network reliability. I has happened both locally and also on a DigitalOcean droplet that typically has a very nice internet connection available. Just posting here to inform that's still something out there going wrong. I cannot identify what makes it fail though, usually a couple of retry will make it work fine, but this has become a regular problem causing automated provisioning with Ansible to fail :(

@vieux vieux closed this in #5848 Jun 2, 2014

@emaillenin

This comment has been minimized.

Copy link

emaillenin commented Jun 4, 2014

This error still exists. Works on 2nd try, though.

root@emaillenin:/usr/lib/apt/methods# cd /var/docker/
root@emaillenin:/var/docker# ./launcher bootstrap app
WARNING: No memory limit support
WARNING: No swap limit support
Your Docker installation is not using aufs, in the past we have had issues with it
If you are unable to bootstrap your image (or stop it) please report the issue at:
https://meta.discourse.org/t/discourse-docker-installation-without-aufs/15639
Unable to find image 'samsaffron/discourse:0.2.1' locally
Pulling repository samsaffron/discourse
b06b7d939b10: Error pulling image (0.2.1) from samsaffron/discourse, unexpected EOF
511136ea3c5a: Download complete
6170bb7b0ad1: Download complete
9cd978db300e: Download complete
89ce7d6fa9eb: Download complete
171e004f19b8: Error downloading dependent layers
2014/06/04 15:20:13 Could not find repository on any of the indexed registries.
Your Docker installation is not working correctly

See: https://meta.discourse.org/t/docker-error-on-bootstrap/13657/18?u=sam
@davidpelaez

This comment has been minimized.

Copy link
Contributor

davidpelaez commented Jun 4, 2014

@emaillenin from what I read in PR #5848 this is fixed but not live because it depends on an update in the public docker index. @unclejack commented there: "@crosbymichael It can be reviewed, but we should wait for the new registry to be live before merging it."

@bbhoss

This comment has been minimized.

Copy link

bbhoss commented Jun 25, 2014

I don't believe this has been fixed. I still get 2014/06/25 13:18:38 Error: EOF when importing from STDOUT, so I doubt it's a registry issue.

@unclejack

This comment has been minimized.

Copy link
Contributor

unclejack commented Jun 25, 2014

@bbhoss The error you've run into has nothing to do with this issue. Please open a new issue.

@bbhoss

This comment has been minimized.

Copy link

bbhoss commented Jun 25, 2014

ok, I will try to investigate more. Does import hit a different function or something? Trying to grok the source.

@runvnc

This comment has been minimized.

Copy link
Contributor

runvnc commented Jul 11, 2014

#4709 Download layers in parallel was closed and referred to this issue by @unclejack, so although I don't actually see a lot of parallel download discussion in this issue that leads me to believe it is the right one for this comment.

I think in here #352 there is some code that at some point downloaded images in parallel.

@unclejack said "The layers of an image can't be downloaded in parallel because each layer relies on the previous one.

The storage backends require the image on which a layer depends on to be already registered before being able to register it. Changing the code to make it pull the layers of the same image in parallel would make the code too complicated, especially since #2461 also requires some changes."

Would it not be possible to adapt @byAtlas 's code to download the images (layers?) to a temporary directory, and then register them with the storage backend after all (or the dependency) downloads finish? If this could save a significant amount of time in downloading, would it not be worth the complication?

@lfn3

This comment has been minimized.

Copy link

lfn3 commented Jul 12, 2014

Hey so as far as I know, my changes didn't actually ever get merged in. #150 ended up with @vieux 's code merged in as far as I know. Although there is some question about if it was eventually reverted in the tail end of #150. There's some other issues (I think) so I'm gonna drag that conversation back over there.

@unclejack

This comment has been minimized.

Copy link
Contributor

unclejack commented Jul 12, 2014

Please don't discuss about parallel pull on this issue. Thanks!

@arungupta2008

This comment has been minimized.

Copy link

arungupta2008 commented Aug 5, 2014

I have MAC laptop my laptop's tar version is
bsdtar 2.8.3 - libarchive 2.8.3

i am creating a tar from other machine (docker save), and using this to other machine but when ran this (sudo docker load --input fedora.tar) but it's creating problem Error: unexpected EOF ?

why ?

@venkat

This comment has been minimized.

Copy link

venkat commented Aug 18, 2014

I am facing this issue and I would love to help/contribute - at least with diagnostics information. I am currently on a 50 Mbps connection but here's what I experience:

$ docker pull training/webapp

Pulling repository training/webapp
31fa814ba25a: Pulling dependent layers
511136ea3c5a: Download complete
f10ebce2c0e1: Downloading [==>                                                ] 1.572 MB/39.17 MB 13m41s

Here's my traceroute:

$ traceroute cdn-registry-1.docker.io
traceroute to cdn-registry-1.docker.io (162.242.195.77), 64 hops max, 52 byte packets
 1  10.1.10.1 (10.1.10.1)  3.449 ms  1.236 ms  0.948 ms
 2  98.210.152.1 (98.210.152.1)  14.668 ms  10.694 ms  10.598 ms
 3  te-4-8-ur01.sffolsom.ca.sfba.comcast.net (68.85.190.29)  9.588 ms  15.685 ms  10.121 ms
 4  68.87.194.70 (68.87.194.70)  16.914 ms  20.454 ms  15.601 ms
 5  he-3-8-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.94.85)  16.120 ms  11.438 ms  16.707 ms
 6  he-2-12-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.89.218)  27.285 ms  35.218 ms  39.955 ms
 7  he-0-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.146)  55.069 ms  55.295 ms  52.276 ms
 8  pos-3-0-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.85.21)  82.443 ms  71.568 ms  71.647 ms
 9  he-0-3-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.89.149)  97.338 ms  91.320 ms  88.521 ms
10  he-0-11-0-0-pe07.ashburn.va.ibone.comcast.net (68.86.83.74)  85.419 ms  87.675 ms  142.057 ms
11  as36248-1-c.ashburn.va.ibone.comcast.net (23.30.206.230)  86.429 ms  84.467 ms  88.504 ms
12  corea-edge7.corea.iad3.rackspace.net (69.20.1.240)  84.910 ms  84.490 ms  86.215 ms
13  corea-core7.iad3.rackspace.net (69.20.2.97)  99.581 ms
    corea-core8.iad3.rackspace.net (69.20.2.99)  86.442 ms
    corea-core7.iad3.rackspace.net (69.20.2.97)  85.931 ms
14  aggr402a-2-core7.iad3.rackspace.net (69.20.3.113)  84.931 ms
    aggr402a-2-core8.iad3.rackspace.net (69.20.3.115)  84.861 ms
    aggr402a-2-core7.iad3.rackspace.net (69.20.3.113)  85.304 ms
15  162.242.195.77 (162.242.195.77)  93.355 ms  83.798 ms  89.214 ms

One thing I would like to know is - is there some way I could get debugging info. on what happens during the docker pull? For example, I would like know the exact URLs of the files it downloads so I can try curl on them. I could not find any debug flag or verbose flag associated with the docker pull command. I tried running it as docker -D pull training/webapp but that didn't help. I am newbie to docker.

@Vishant0031

This comment has been minimized.

Copy link

Vishant0031 commented Feb 25, 2015

I am getting consistently this error while docker pull:
"FATA[0563] Error pulling image [myimage] from my-private-registry, ApplyLayer exit status 1 unexpected EOF"

Any ideas what this could be?

behavior is same for
docker version 1.3.3 docker 1.4.x

@dmp42

This comment has been minimized.

Copy link
Contributor

dmp42 commented Feb 25, 2015

@Vish0007 this issue here is closed - your problem is likely unrelated.
Please open a new issue, providing at least: docker info docker version and both docker daemon logs (in debug mode docker -d -D) and docker registry logs, version and configuration (since you are running a private registry).
Thanks.

@dmp42

This comment has been minimized.

Copy link
Contributor

dmp42 commented Feb 27, 2015

@Vish0007 Like I said in my previous comment: This issue here is closed - your problem is likely unrelated. Please open a new issue

Also, you should test if possible with a recent version of docker (you are using 1.3 - 1.5 is the last stable).

@Vishant0031

This comment has been minimized.

Copy link

Vishant0031 commented Feb 28, 2015

Ah.
Sure I will open.
Trying on latest version of docker does not help.

@Vishant0031

This comment has been minimized.

Copy link

Vishant0031 commented Feb 28, 2015

@asheshambasta

This comment has been minimized.

Copy link

asheshambasta commented Mar 14, 2015

Ran into this when trying: docker pull dockerfile/java
Got (after 10+ tries):
2015/03/14 12:01:35 Could not find repository on any of the indexed registries.
Docker version: Docker version 1.0.1, build 990021a

@thaJeztah

This comment has been minimized.

Copy link
Member

thaJeztah commented Mar 14, 2015

@asheshambasta docker 1.0.1 is really old! perhaps you can try updating to the current version (1.5).

Also, dockerfiles/java is not the official java image, the official image can be found here; https://registry.hub.docker.com/u/library/java/ and is simply called java

@asheshambasta

This comment has been minimized.

Copy link

asheshambasta commented Mar 14, 2015

Ah, I see. I’ll update docker and let you guys know. And this is my first day with docker and I’m impressed to see some activity here!

On 14 Mar 2015, at 13:14, Sebastiaan van Stijn notifications@github.com wrote:

@asheshambasta https://github.com/asheshambasta docker 1.0.1 is really old! perhaps you can try updating to the current version (1.5).

Also, dockerfiles/java is not the official java image, the official image can be found here; https://registry.hub.docker.com/u/library/java/ https://registry.hub.docker.com/u/library/java/ and is simply called java


Reply to this email directly or view it on GitHub #2461 (comment).

@thaJeztah

This comment has been minimized.

Copy link
Member

thaJeztah commented Mar 14, 2015

@asheshambasta you're welcome. Please keep in mind this is not a support forum. If you have questions on running/using docker, please use the #docker IRC channel, the docker-user or StackOverflow

Also (see #2461 (comment)) this issue is closed, so if you run into an issue with the latest version of docker, please open a new issue in stead.

@moby moby locked and limited conversation to collaborators Mar 16, 2015

@dmp42

This comment has been minimized.

Copy link
Contributor

dmp42 commented Mar 16, 2015

The issue originally described here has been fixed, and is now closed.

If you see the same symptoms:

  • first check that you are using a recent enough docker version (1.5 recommended)
  • if you still see these symptoms with docker 1.5, then it's certainly a different issue: please open a new ticket describing exactly what happens, plus docker version + docker info + your docker daemon logs in debug mode

Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.