I am facing this weird issue, that docker becomes unresponsive but the containers keep on running and i start getting:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Then I have to restart docker service to make it work. In Journalctl there are no such errors that could give a clue. It only shows error like level=error msg="collecting stats for b960555073339f30c7ce9fcb2abb01d15ab50ca0451d2b77ed1212933e9c5a86: no such container"
When i check the docker service status through systemctl status docker
it shows that the docker service is up and running without any error.
Can someone please help me figuring out this issue?
Output of docker info
is:
Server:
- Containers: 149
Running: 70
Paused: 0
Stopped: 79
- Server Version: 19.03.15
- Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: true
Native Overlay Diff: true
- Logging Driver: json-file
- Cgroup Driver: cgroupfs
- Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
- Swarm: inactive
- Runtimes: runc
- Default Runtime: runc
- Init Binary: docker-init
- containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b
- runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
- init version: fec3683
- Security Options:
seccomp
Profile: default
- Kernel Version: 3.10.0-1127.19.1.el7.x86_64
- Operating System: Red Hat Enterprise Linux
- OSType: linux
- Architecture: x86_64
- CPUs: 88
- Total Memory: 754.3GiB