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

Docker pushing FATA[3717] FATA[3791] #11449

Closed
marianoeramirez opened this issue Mar 17, 2015 · 7 comments
Closed

Docker pushing FATA[3717] FATA[3791] #11449

marianoeramirez opened this issue Mar 17, 2015 · 7 comments

Comments

@marianoeramirez
Copy link

Hi, i want to submit this issue, because i have all the day try to pushing a image to a private repository and it throw error.

There is mi error:


mariano@mariano-laptop:/media/mariano/B2FE2042FE1FFD6B/bright/docker$ sudo docker push bomba1990/firefly
[sudo] password for mariano: 
The push refers to a repository [bomba1990/firefly] (len: 1)
Sending image list
Pushing repository bomba1990/firefly (1 tags)
511136ea3c5a: Image already pushed, skipping 
3b363fd9d7da: Image already pushed, skipping 
607c5d1cca71: Image already pushed, skipping 
f62feddc05dc: Image already pushed, skipping 
8eaa4ff06b53: Image already pushed, skipping 
b0f0f9a62374: Image already pushed, skipping 
c4490c63e30c: Pushing [=====================>                             ] 368.3 MB/872.1 MB 1h22m14s
FATA[3717] Failed to upload layer: Put https://cdn-registry-1.docker.io/v1/images/c4490c63e30c5efda8bbde5678b9746eed3553fef15cd1b37caf05b32026f968/layer: EOF 
mariano@mariano-laptop:/media/mariano/B2FE2042FE1FFD6B/bright/docker$ sudo docker push bomba1990/firefly
[sudo] password for mariano: 
The push refers to a repository [bomba1990/firefly] (len: 1)
Sending image list
Pushing repository bomba1990/firefly (1 tags)
511136ea3c5a: Image already pushed, skipping 
3b363fd9d7da: Image already pushed, skipping 
607c5d1cca71: Image already pushed, skipping 
f62feddc05dc: Image already pushed, skipping 
8eaa4ff06b53: Image already pushed, skipping 
b0f0f9a62374: Image already pushed, skipping 
c4490c63e30c: Pushing [==================================================>] 872.1 MB/872.1 MB
FATA[3791]  
@phemmer
Copy link
Contributor

phemmer commented Mar 18, 2015

The docker daemon logs might have some better insight into the issue. Could you provide them for the timeframe surrounding the failed push?

@marianoeramirez
Copy link
Author

Excume, but where i find those logs?

I want to comment you, that i successfully push the image, but i has to upload it to a server with ftp and push it from the server. I think the problem with my machine is the speed of upload, because mi machine take 4 hours to upload the image, and from the server only 5 min.

@phemmer
Copy link
Contributor

phemmer commented Mar 18, 2015

It depends on your OS and the docker package you installed (how it configured the service).

2 likely locations are: /var/log/docker.log, or if using systemd, journalctl -u docker.service.

@dmp42
Copy link
Contributor

dmp42 commented Mar 19, 2015

Hi @Bomba1990

Can you also copy the output of docker version and docker info?

Indeed, if you uplink is extremely slow (you mentioned 4 hours to upload the layer) there might be timeouts...

Thanks.

@marianoeramirez
Copy link
Author

Yes my uplink is 50kb/seg.

Version:

Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8

info:

Containers: 5
Images: 91
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 101
Execution Driver: native-0.2
Kernel Version: 3.11.0-12-generic
Operating System: Ubuntu 13.10
CPUs: 4
Total Memory: 2.866 GiB
Name: mariano-laptop
ID: ZHPQ:RWQU:KGA3:TQQ6:O6BM:WY2H:LTT2:A3WH:EIHE:YL6X:XEHJ:LUDK
Username: bomba1990
Registry: [https://index.docker.io/v1/]
WARNING: No swap limit support

@dmp42
Copy link
Contributor

dmp42 commented Mar 19, 2015

@Bomba1990 ok thanks.

Do you have the daemon logs? (re #11449 (comment))

@unclejack
Copy link
Contributor

The environment on which this issue was encountered had at least two major issues:

  1. the distribution was an unsupported Ubuntu 13.10 which is no longer being updated, not for security or for bug fixes
  2. the Docker version is pretty old now.

Please upgrade the OS to something supported (such as Ubuntu 14.04), install the latest Docker release and use the latest version of the registry.

I'll close this issue now because API changes have been made to the registry. Please feel free to comment if you run into this issue with the latest releases.

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

5 participants