RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

docker-registry has been obsoleted by docker-distribution. Please file a bug against docker-distribution if this issue exists with it as well..