Red Hat Bugzilla – Bug 1466479
level=fatal msg="can't create unix socket /var/run/docker.sock: is a directory"
Last modified: 2018-06-15 18:14:10 EDT
Description of problem: Docker gets terminated at the same time as OpenShift trying to restart a pod that mounts /var/run/docker.sock. Causing /var/run/docker.sock to be created as a directory. When docker starts again it fails with the following error: 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-31.git3a6eaeb.el7.x86_64 Steps to Reproduce: 1. Start container mounting var/run/docker.sock at the same time as killing docker. Actual results: var/run/docker.sock is created as a directory Expected results: fail to start the container while docker shuts down. Additional info: Upstream issue: https://github.com/moby/moby/issues/30348 Reproducer is in commit message. Possible fix: https://github.com/moby/moby/pull/33330/commits/7318eba5b2f8bb4b867ca943c3229260ca98a3bc
Are you using autostarted containers with the /var/run/docker.sock mounted into them?
@Dan These containers are configured as a daemonset in OpenShift. Using this template. https://github.com/kubernetes/charts/blob/master/stable/telegraf/templates/daemonset.yaml Issue was worked around by mounting /var/run to another location.
*** Bug 1466867 has been marked as a duplicate of this bug. ***
THis should no longer be an issue.