Ask questionsupgrade docker-18.09.2-ce , shim.sock: bind: address already in use: unknown
<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see https://github.com/moby/moby/blob/master/CONTRIBUTING.md#reporting-other-issues
The GitHub issue tracker is for bug reports and feature requests. General support for docker can be found at the following locations:
General support for moby can be found at the following locations:
Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->
<!-- Error": "failed to listen to abstract unix socket "/containerd-shim/moby/a1c1d1c293322d2a55544d1a1e2fbd897e5ad937c6461fb0c8785f15af585371/shim.sock": listen unix \u0000/containerd-shim/moby/a1c1d1c293322d2a55544d1a1e2fbd897e5ad937c6461fb0c8785f15af585371/shim.sock: bind: address already in use: unknown",-->
Steps to reproduce the issue: 1.upgrade docker from 18.03.1-ce to 18.09.2-ce
some container show failed to bind address I have "ps -ef|grep mysqld" and ss -nlp|grep 3306 ,cleaned process
docker start xxxx , it still show the some error
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Client: Version: 18.09.2 API version: 1.39 Go version: go1.10.6 Git commit: 6247962 Built: Sun Feb 10 04:13:27 2019 OS/Arch: linux/amd64 Experimental: false Server: Docker Engine - Community Engine: Version: 18.09.2 API version: 1.39 (minimum version 1.12) Go version: go1.10.6 Git commit: 6247962 Built: Sun Feb 10 03:47:25 2019 OS/Arch: linux/amd64 Experimental: false
Containers: 22 Running: 20 Paused: 0 Stopped: 2 Images: 41 Server Version: 18.09.2 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 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: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec init version: fec3683 Security Options: seccomp Profile: default Kernel Version: 4.4.152-1.el7.elrepo.x86_64 Operating System: CentOS Linux 7 (Core) OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 7.67GiB Name: dev-rac-agent-01 ID: FNDH:GCFF:P7GX:7SU3:F3JY:2NSS:DSGX:7WOT:HDA4:TQDC:LT5T:SPDF Docker Root Dir: /data/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: bridge-nf-call-iptables is disabled WARNING: bridge-nf-call-ip6tables is disabled
Additional environment details (AWS, VirtualBox, physical, etc.): CentOS Linux release 7.5.1804 (Core) on xen
anyone has this issue ?
Answer questions elfgoh
I experience a similar issue on version 18.09.3
835400486f5a 60b7495196e2 "/app/core-vitals -c…" 7 weeks ago Exited (1) 4 days ago core-vitals-25 Mon 06 May 2019 11:02:04 AM $ docker start 835400486f5a Error response from daemon: failed to listen to abstract unix socket "/containerd-shim/moby/835400486f5a9eb0466c6fd1e7a53bae969aaa56dc23b9928179f5f7d5c4988e/shim.sock": listen unix /containerd-shim/moby/835400486f5a9eb0466c6fd1e7a53bae969aaa56dc23b9928179f5f7d5c4988e/shim.sock: bind: address already in use: unknown Error: failed to start containers: 835400486f5a
Deleting the container and recreating seems to resolve the issue