Docker Community Forums

Share and learn in the Docker community.

Docker error /var/run/docker.sock->@: write: broken pipe

Getting docker.sock broken pipes when trying to start Kubernetes Kubelet service,

Apr 08 20:04:55 xxxxxxx-xxxxx dockerd[28542]: time=“2019-04-08T20:04:55.950992420Z” level=error msg=“Handler for GET /v1.38/images/json returned error: write unix /var/run/docker.sock->@: write: broken pipe”
Apr 08 20:04:55 xxxxxxx-xxxxxdockerd[28542]: time=“2019-04-08T20:04:55.951267897Z” level=error msg=“Handler for GET /v1.38/images/json returned error: write unix /var/run/docker.sock->@: write: broken pipe”

From Kubelet

Apr 08 20:05:06xxxxxxx-xxxxx kubelet[28896]: E0408 20:05:06.311619 28896 kubelet.go:1282] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data in memory>
Apr 08 20:05:06 xxxxxxx-xxxxx kubelet[28896]: E0408 20:05:06.311916 28896 event.go:200] Unable to write event: ‘Post https://172.24.4.14:6443/api/v1/namespaces/default/events: dial tcp 172.24.4.14:6443: connect: connection refused’ (ma>
Apr 08 20:05:06 xxxxxxx-xxxxx kubelet[28896]: I0408 20:05:06.312333 28896 server.go:343] Adding debug handlers to kubelet server.

Debug Logs

Apr 08 20:27:00 smccully-amd dockerd[31775]: time=“2019-04-08T20:27:00.054052856Z” level=debug msg=“Calling GET /v1.38/containers/json?all=1&filters=%7B%22label%22%3A%7B%22io.kubernetes.docker.type%3Dpodsandbox%22%3Atrue%7D%7D&limit=0”
Apr 08 20:27:00 smccully-amd dockerd[31775]: time=“2019-04-08T20:27:00.071869982Z” level=debug msg=“FIXME: Got an API for which error does not match any expected type!!!: write unix /var/run/docker.sock->@: write: broken pipe” error_type="*net.OpError" module=api
Apr 08 20:27:00 smccully-amd dockerd[31775]: time=“2019-04-08T20:27:00.071907683Z” level=error msg=“Handler for GET /v1.38/images/json returned error: write unix /var/run/docker.sock->@: write: broken pipe”
Apr 08 20:27:00 smccully-amd dockerd[31775]: time=“2019-04-08T20:27:00.071925797Z” level=debug msg=“FIXME: Got an API for which error does not match any expected type!!!: write unix /var/run/docker.sock->@: write: broken pipe” error_type="*net.OpError" module=api

No answer to this? Seems like a critical problem. I’m seeing this now also.

$ docker info

Containers: 0

Running: 0

Paused: 0

Stopped: 0

Images: 178

Server Version: 18.09.5

Storage Driver: overlay2

Backing Filesystem: extfs

Supports d_type: true

Native Overlay Diff: true

Logging Driver: json-file

Cgroup Driver: cgroupfs

Plugins:

Volume: local

Network: bridge host 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: e6b3f5632f50dbc4e9cb6288d911bf4f5e95b18e

runc version: 6635b4f0c6af3810594d2770f662f34ddc15b40d

init version: fec3683

Security Options:

apparmor

seccomp

Profile: default

Kernel Version: 4.15.0-1032-aws

Operating System: Ubuntu 18.04.2 LTS

OSType: linux

Architecture: x86_64

CPUs: 4

Total Memory: 15.21GiB

Name: ip-10-23-3-178

ID: GTKW:PXVG:VF7Y:G5YF:TOOS:P3TG:3SUU:QNBU:YAUE:OEF6:KAB6:Z54R

Docker Root Dir: /var/lib/docker

Debug Mode (client): false

Debug Mode (server): false

Registry: https://index.docker.io/v1/

Labels:

Experimental: false

Insecure Registries:

127.0.0.0/8

Live Restore Enabled: false

Product License: Community Engine

WARNING: No swap limit support

$ cat /etc/os-release

NAME=“Ubuntu”

VERSION=“18.04.2 LTS (Bionic Beaver)”

ID=ubuntu

ID_LIKE=debian

PRETTY_NAME=“Ubuntu 18.04.2 LTS”

VERSION_ID=“18.04”

HOME_URL=“https://www.ubuntu.com/

SUPPORT_URL=“https://help.ubuntu.com/

BUG_REPORT_URL=“https://bugs.launchpad.net/ubuntu/

PRIVACY_POLICY_URL=“https://www.ubuntu.com/legal/terms-and-policies/privacy-policy

VERSION_CODENAME=bionic

UBUNTU_CODENAME=bionic