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.
Bug 1340468 - Regression: Can not complete docker push on NFS in Docker Distribution 2.4
Summary: Regression: Can not complete docker push on NFS in Docker Distribution 2.4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker-distribution
Version: 7.2
Hardware: All
OS: All
urgent
urgent
Target Milestone: rc
: ---
Assignee: Michal Minar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-27 13:29 UTC by Matthew Robson
Modified: 2020-04-15 14:30 UTC (History)
1 user (show)

Fixed In Version: docker-distribution-2.5.0-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: A regression was introduced in docker registry 2.4 where file descriptors weren't closed during blob uploads. Consequence: This has caused image push failures when the registry was running on top of NFS file system. Fix: A new version of upstream docker registry is available with a fix to the leaking file descriptors. Result: Image pushes now succeed on NFS file systems.
Clone Of:
Environment:
Last Closed: 2016-12-06 17:42:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1338871 0 unspecified CLOSED [extras-rhel-7.2.5] rebase docker-distribution to v2.4.1 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2016:2892 0 normal SHIPPED_LIVE docker-distribution bug fix and enhancement update 2016-12-06 22:40:46 UTC

Description Matthew Robson 2016-05-27 13:29:41 UTC 
Description of problem:
A regression in Docker Distribution 2.4 causes a file descriptor leak rendering the docker registry unusable for pushes while using NFS.  It leads to an innocuous 'unexpected HTTP status: 500 Internal Server Error' on every push.

Version-Release number of selected component (if applicable):
2.4.0

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Docker Pushes Fail 100%

Expected results:
Docker Push Should Succeed

Additional info:
Comment 2 Matthew Robson 2016-05-27 13:33:50 UTC 
This is fixed in docker-distribution 2.4.1 through https://github.com/docker/distribution/pull/1666
Comment 4 Michal Minar 2016-10-06 12:30:31 UTC 
Matthew,

the latest docker-registry we ship for rhel7 is 0.9.1. The same applies to Fedora.

Do you perhaps refer to Product/Component  "OpenShift Container Platform/Image Registry"?

The version of docker-registry in released OSE 3.2 is v2.2.1 though.
Comment 5 Michal Minar 2016-10-06 14:00:49 UTC 
Oh, we have also docker-distribution component in brew. Please, disregard my previous comment. The latest released docker-distribution is 2.5.0. And as you mention in comment 2, it should resolve the issue.

Can you please confirm?
Comment 9 Luwen Su 2016-11-14 15:49:43 UTC 
docker-distribution-2.5.1-1.el7.x86_64:

In nfs server host:
# cat /etc/exports
/nfs-test *(rw,sync,no_root_squash)

In docker-distribution server host:
# mount -t nfs 10.66.3.108:/nfs-test /var/lib/registry
# df -TH
10.66.3.108:/nfs-test nfs4       19G  3.3G   16G  18% /var/lib/registry

# cat /etc/docker-distribution/registry/config.yml
version: 0.1
log:
  fields:
    service: registry
storage:
    cache:
        layerinfo: inmemory
    filesystem:
        rootdirectory: /var/lib/registry
http:
    addr: :5000

# docker-latest push localhost:5000/busybox
The push refers to a repository [localhost:5000/busybox]
8ac8bfaff55a: Pushed 
latest: digest: sha256:1359608115b94599e5641638bac5aef1ddfaa79bb96057ebf41ebc8d33acf8a7 size: 527
Comment 11 errata-xmlrpc 2016-12-06 17:42:55 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2892.html
Note You need to log in before you can comment on or make changes to this bug.