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 1299519 - docker pull hangs with "Layer already being pulled by another client"
Summary: docker pull hangs with "Layer already being pulled by another client"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-18 15:08 UTC by Jake Hunsaker
Modified: 2019-12-16 05:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-03 20:07:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jake Hunsaker 2016-01-18 15:08:49 UTC
Description of problem:

A 'docker pull' command will hang intermittently (meaning occasionally when docker pulls are run, not that one docker pull is occasionally hanging) with the following for example:

[root@sd-e6ec-7fc8 ~]# docker pull tomcat:7.0
Trying to pull repository docker.io/library/tomcat ... 7.0: Pulling from library/tomcat
6d1ae97ee388: Verifying Checksum
8b9a99209d5c: Pulling fs layer
2e05a52ffd47: Pulling fs layer
9fdaeae348bb: Pulling fs layer
67d05086af43: Pulling fs layer
2e9d1ec89d66: Pulling fs layer
1afb0d51eee0: Pulling fs layer
5cb24a57fa37: Pulling fs layer
110c2f290b04: Pulling fs layer
966dcd51a14f: Pulling fs layer
8a57ce404f1b: Pulling fs layer
e1b97b980d07: Pulling fs layer
0e74df9853d7: Pulling fs layer
20d94860039d: Verifying Checksum
ad4e266e1bd1: Pulling fs layer
13091c61ed8d: Pulling fs layer
6c6bae9ca483: Pulling fs layer
068fc2e47624: Pulling fs layer
373f6ee029ce: Layer already being pulled by another client. Waiting.


Version-Release number of selected component (if applicable):
 docker-1.8.2-10.el7.x86_64

How reproducible:
Reliably for customer

Steps to Reproduce:
1. Try pulling from either docker.io or registry.access.redhat.com
2.
3.

Actual results:
Intermittently, the pull will hang with the above output

Expected results:
Image should be pulled, or an error should be given.

Additional info:


Restarting the docker daemon sometimes has an effect. The customer reports that after restarting the daemon, they can either pull the image normally or the pull will hang again with the same "already being pulled" message - no indication yet of any reason why this sometimes works and sometimes doesn't.

Comment 12 Daniel Walsh 2016-06-03 20:07:55 UTC
docker-1.9 has been out for a while so I am going to close this as fixed in the current release.


Note You need to log in before you can comment on or make changes to this bug.