Bug 1466867

Summary:	Docker doesn't start with error "can't create unix socket /var/run/docker.sock: is a directory"
Product:	Red Hat Enterprise Linux 7	Reporter:	Alexis Solanas <asolanas>
Component:	docker	Assignee:	Antonio Murdaca <amurdaca>
Status:	CLOSED DUPLICATE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	amurdaca, asolanas, dornelas, jamills, lsm5, nithinmanglore
Target Milestone:	rc	Keywords:	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:	2017-11-27 08:39:37 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:
Bug Depends On:
Bug Blocks:	1186913

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 ***