Hide Forgot
Description of problem: Customer has defined garbage collection but having the problem with docker: image_manager.go:135] [ImageManager] Failed to monitor images: Get http://unix.sock/images/json: dial unix /var/run/docker.sock: no such file or directory The normal running of nodes is ok, everything is working. Also the /var/run/docker.sock exists and is accessible. ls -l /var/run/docker.sock srw-rw----. 1 root root 0 Oct 27 12:37 /var/run/docker.sock Version-Release number of selected component (if applicable): OpenShift Container Platform 3.2.0 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Just adding that version of docker is: $ docker info Containers: 6 Running: 6 Paused: 0 Stopped: 0 Images: 26 Server Version: 1.10.3 Storage Driver: devicemapper Pool Name: docker--vg-docker--pool Pool Blocksize: 524.3 kB Base Device Size: 10.74 GB Backing Filesystem: xfs Data file: Metadata file: Data Space Used: 7.317 GB Data Space Total: 12.87 GB Data Space Available: 5.551 GB Metadata Space Used: 1.368 MB Metadata Space Total: 33.55 MB Metadata Space Available: 32.19 MB Udev Sync Supported: true Deferred Removal Enabled: true Deferred Deletion Enabled: true Deferred Deleted Device Count: 0 Library Version: 1.02.107-RHEL7 (2016-06-09) Execution Driver: native-0.2 Logging Driver: json-file Plugins: Volume: local Network: bridge null host Authorization: rhel-push-plugin Kernel Version: 3.10.0-327.28.2.el7.x86_64 Operating System: OpenShift Enterprise OSType: linux Architecture: x86_64 Number of Docker Hooks: 2 CPUs: 2 Total Memory: 7.632 GiB
/var/run/docker.sock is removed when docker daemon is stopped. Running $(systemctl status docker) when this condition is found should verify this. Assuming the nodes are using journald logging, then $(journalctl -u docker) should produce the logs entries from the docker daemon.
What's the steps to produce the issue ? Could you provide more info?
Hello, the problem is with the ImageManager, he can't connect to the /var/run/docker.sock [ImageManager] Failed to monitor images: Get http://unix.sock/images/json: dial unix /var/run/docker.sock: no such file or directory ls -l /var/run/docker.sock srw-rw----. 1 root root 0 Oct 27 12:37 /var/run/docker.sock The /var/run/docker.sock exists, the docker is running correctly. Both Docker and OpenShift are running under root, so there should be no issue with the user. Also there is: ll /usr/lib/systemd/system/docker.service.d/docker-sdn-ovs.conf -rw-r--r--. 1 root root 61 Jul 14 23:31 /usr/lib/systemd/system/docker.service.d/docker-sdn-ovs.conf $ cat /usr/lib/systemd/system/docker.service.d/docker-sdn-ovs.conf [Service] EnvironmentFile=-/run/openshift-sdn/docker-network $ cat /run/openshift-sdn/docker-network # This file has been modified by openshift-sdn. DOCKER_NETWORK_OPTIONS='-b=lbr0 --mtu=1450'
Is this still an issue?