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 1466867 - Docker doesn't start with error "can't create unix socket /var/run/docker.sock: is a directory"
Summary: Docker doesn't start with error "can't create unix socket /var/run/docker.soc...
Keywords:
Status: CLOSED DUPLICATE of bug 1466479
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Antonio Murdaca
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1186913
TreeView+ depends on / blocked
 
Reported: 2017-06-30 15:25 UTC by Alexis Solanas
Modified: 2021-09-09 12:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-27 08:39:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexis Solanas 2017-06-30 15:25:53 UTC
Description of problem:

 docker start fails with the error message: 
  
   level=fatal msg="can't create unix socket /var/run/docker.sock: is a directory"

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

 docker-1.12.6-28

How reproducible:

 Unknown, it happens randomly when restarting docker

Steps to Reproduce:

1.
2.
3.

Actual results:

 docker fails to start

Expected results:

 docker starts normally

Additional info:

 This is being tracked by the following upstream issue:

  "can't create unix socket /var/run/docker.sock: is a directory #30348"
   https://github.com/moby/moby/issues/30348

Comment 2 Daniel Walsh 2017-07-02 10:07:30 UTC
How is the container being started, is it autostarted by docker?

Comment 3 Nitin 2017-07-03 15:16:12 UTC
This issue i observed, when i do automated playbook upgrade. 
After the draining of all pods and restart of docker service.

Comment 7 Alexis Solanas 2017-11-27 08:39:37 UTC

*** This bug has been marked as a duplicate of bug 1466479 ***


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