Bug 1420657

Summary: docker push to local Docker v1 Registry fails occasionally
Product: Red Hat Enterprise Linux 7 Reporter: Marko Myllynen <myllynen>
Component: docker-registryAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED EOL QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: lsm5, thrcka
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-10 12:50:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
push-log.txt none

Description Marko Myllynen 2017-02-09 08:18:51 UTC 
Created attachment 1248747 [details]
push-log.txt

Description of problem:
I've seen the below kind of error a few times, usually push works all ok:

The push refers to a repository [registry.example.com:5000/redhat-sso-7/sso70-openshift]
f69c4dd03a49: Waiting 
c57533510290: Waiting 
899e90251367: Waiting 
2f2c71ba7d1a: Pushing 195.8 MB/195.8 MB
a2de66622680: Image successfully pushed 
22426f366c51: Already exists 
94b2db70f747: Already exists 
Failed to upload layer: Put http://registry.example.com:5000/v1/images/05f89e41dbbca067e3d76a63cb66fc44e6aa6bf92fe0b4a8f87f983afd1628d2/layer: read tcp 192.168.122.1:42008->192.168.122.1:5000: read: connection reset by peer

Since v1 registries are rarely used I'm not sure how much effort is warranted here (I'm not eager to spend much time on this) but since I happened to capture the case when logging was set to debug I'm at least reporting this here.

I'm attaching the logs which contain all the information available.

Version-Release number of selected component (if applicable):
docker-registry-0.9.1-7.el7.x86_64
Comment 2 Lokesh Mandvekar 2019-04-10 12:50:38 UTC 
docker-registry has been obsoleted by docker-distribution. Please file a bug against docker-distribution if this issue exists with it as well..