docker
docker copied to clipboard
write unix /var/run/docker.sock->@: write: broken pipe
Output of docker version
:
lient:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-63.mt20190220.gitd365784.el7.centos.x86_64
Go version: go1.7.5
Git commit: d365784/1.13.1
Built: Wed Feb 20 03:10:55 2019
OS/Arch: linux/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-63.mt20190220.gitd365784.el7.centos.x86_64
Go version: go1.7.5
Git commit: d365784/1.13.1
Built: Wed Feb 20 03:10:55 2019
OS/Arch: linux/amd64
Experimental: false
Output of docker info
:
Containers: 44
Running: 44
Paused: 0
Stopped: 0
Images: 35
Server Version: 1.13.1
Storage Driver: devicemapper
Pool Name: dockervg-thinpool
Pool Blocksize: 524.3 kB
Base Device Size: 10.74 GB
Backing Filesystem: ext4
Data file:
Metadata file:
Data Space Used: 55.22 GB
Data Space Total: 973.7 GB
Data Space Available: 918.5 GB
Metadata Space Used: 19.8 MB
Metadata Space Total: 10.25 GB
Metadata Space Available: 10.23 GB
Thin Pool Minimum Free Space: 97.37 GB
Udev Sync Supported: true
Deferred Removal Enabled: true
Deferred Deletion Enabled: true
Deferred Deleted Device Count: 0
Library Version: 1.02.140-RHEL7 (2017-05-03)
Logging Driver: json-file
Cgroup Driver: systemd
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc docker-runc
Default Runtime: docker-runc
Init Binary: /usr/libexec/docker/docker-init-current
containerd version: d365784586ef8dfc171f524aa329e928dc355c76 (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: e9ab997cfc4151ebcca8e54cf047311121fd4849 (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: 5b117de7f824f3d3825737cf09581645abbe35d4 (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
seccomp
WARNING: You're not using the default seccomp profile
Profile: /etc/docker/seccomp.json
Kernel Version: 3.10.0-862.mt20190308.130.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 64
Total Memory: 251.7 GiB
Name: tx-cloudinf-node-tencentbj19.mt
ID: XUTN:4ZK5:RGPJ:O3F2:BEVF:SJXT:YYUQ:BEES:YEWS:42QF:TA52:A5CK
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Registry Mirrors:
http://127.0.0.1:65001
registryonline-hulk.sankuai.com
Live Restore Enabled: true
Registries: docker.io (secure)
Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue: 1.Unclear what caused the operation, suddenly there will be "error: write unix /var/run/docker.sock->@: write: broken pipe"
Describe the results you received: Failed to start container
Describe the results you expected: Start the container successfully
Additional information you deem important (e.g. issue happens only occasionally): docker.log
Have you played with podman
? The team supporting containers in RHEL is moving away from Docker to other container tools. Podman, Buildah for RHEL7 container workload, and CRI-O for Kubernetes/OpenShift
Have you played with
podman
? The team supporting containers in RHEL is moving away from Docker to other container tools. Podman, Buildah for RHEL7 container workload, and CRI-O for Kubernetes/OpenShift
Did docker not update the code after that?
We are locked into an older version of Docker for kubernetes/openshift support.
@rhatdan We found that many bugs fixed on moby were not fixed on projectatomic / docker. Are you planning to no longer maintain and update the docker-1.13.1-rhel branch?
@rhatdan If we replace docker with podman, does Kubernetes need to change?
Yes we have moved on from Docker to Podman in Fedora as well as RHEL/Centos. Kubernetes should be using CRI-O instead of Docker. Podman is a command line tool, not a CRI for use with the kublet.