Your message dated Thu, 21 Jun 2018 02:53:59 +1000
with message-id <11025639.qN1Nbj1WgW@deblab>
and subject line Done: docker.io: Docker fails to listen on the expected unix
socket
has caused the Debian Bug report #856885,
regarding docker.io: Docker fails to listen on the expected unix socket
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
856885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856885
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: docker.io
Version: 1.11.2~ds1-6
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
docker, in its default configuration on stretch, is setup with systemd
socket activation. The socket systemd listens to is
/var/run/docker.sock, but the current version of docker seems to
expect /var/run/docker/libcontainerd/docker-containerd.sock
The net result is that any docker-* operation hangs, making Docker unuseable.
Symlinking /var/run/docker/libcontainerd/docker-containerd.sock to
/var/run/docker.sock and restarting docker “solved” the issue.
I have no non-default configuration in /etc/docker or /etc/default/docker.
> % docker ps
> [hangs]
>
> % systemctl status docker.service
> ● docker.service - Docker Application Container Engine
> Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor
> preset: enabled)
> Active: activating (start) since Sun 2017-03-05 14:53:04 EST; 13s ago
> Docs: https://docs.docker.com
> Main PID: 27026 (docker)
> Tasks: 8
> Memory: 5.1M
> CPU: 97ms
> CGroup: /system.slice/docker.service
> └─27026 /usr/bin/docker daemon -H fd://
>
> Mar 05 14:53:04 harbard.iaik.tugraz.at systemd[1]: Starting Docker
> Application Container Engine...
> Mar 05 14:53:04 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:04.983760764-05:00" level=info msg="New containerd
> process, pid: 27032\n"
> Mar 05 14:53:05 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:05.001118207-05:00" level=fatal msg="bad listen
> address format /var/run/docker/libcontainerd/docker-containerd.sock, expected
> proto://address"
> Mar 05 14:53:10 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:10.986449214-05:00" level=info msg="New containerd
> process, pid: 27053\n"
> Mar 05 14:53:11 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:11.011430719-05:00" level=fatal msg="bad listen
> address format /var/run/docker/libcontainerd/docker-containerd.sock, expected
> proto://address"
> Mar 05 14:53:21 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:21.289129964-05:00" level=info msg="New containerd
> process, pid: 27065\n"
> Mar 05 14:53:21 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:21.309476765-05:00" level=fatal msg="bad listen
> address format /var/run/docker/libcontainerd/docker-containerd.sock, expected
> proto://address"
> Mar 05 14:53:38 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:38.734083204-05:00" level=info msg="New containerd
> process, pid: 27097\n"
> Mar 05 14:53:38 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:38.752141814-05:00" level=fatal msg="bad listen
> address format /var/run/docker/libcontainerd/docker-containerd.sock, expected
> proto://address"
> Mar 05 14:53:57 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:57.324349682-05:00" level=info msg="New containerd
> process, pid: 27128\n"
> Mar 05 14:53:57 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:53:57.349952538-05:00" level=fatal msg="bad listen
> address format /var/run/docker/libcontainerd/docker-containerd.sock, expected
> proto://address"
> Mar 05 14:55:08 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:55:08.828955857-05:00" level=info msg="New containerd
> process, pid: 27174\n"
> Mar 05 14:55:08 harbard.iaik.tugraz.at docker[27026]:
> time="2017-03-05T14:55:08.852871735-05:00" level=fatal msg="bad listen
> address format /var/run/docker/libcontainerd/docker-containerd.sock, expected
> proto://address"
Best,
nicoo
- -- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages docker.io depends on:
ii adduser 3.115
ii containerd 0.2.3~git20161117.78.03e5862~ds1-1
ii init-system-helpers 1.47
ii iptables 1.6.0+snapshot20161117-5
ii libapparmor1 2.11.0-2
ii libc6 2.24-9
ii libdevmapper1.02.1 2:1.02.137-1
ii libsqlite3-0 3.16.2-2
ii libsystemd0 232-18
ii runc 0.1.1+dfsg1-2
Versions of packages docker.io recommends:
ii ca-certificates 20161130
ii cgroupfs-mount 1.3
ii git 1:2.11.0-2
ii xz-utils 5.2.2-1.2+b1
Versions of packages docker.io suggests:
ii aufs-tools 1:4.1+20161219-1
pn btrfs-progs <none>
ii debootstrap 1.0.88
pn docker-doc <none>
pn rinse <none>
ii zfsutils-linux [zfsutils] 0.6.5.9-2
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAli8b30ZHG5pY29sYXNA
YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z4zHAD/9iMRMCtaOfMsn3r7TZLxXU
OnXDx0RuxHhIkRhrlM1O4qEi2GCn4RF6rDV4rdx2a4S73IGXySVAri2dJBuOklzq
EKyf/LMqenpx7HueO394ic2S9i9CygsBJwkhIZrSYLkLnLwXafl9kwh8jI+in4QC
ntzBv0RvI0E9n4H9Ue0qwrhJuBC/yXdaoFtdyAxnk0SiKcSDVadOgElsl/OPQP6j
iApSUZEnQGNjHjFJnLuHJ292u2Jc2mqbfRpu2uHrZIoB2ZbSIVw3t1sHER09DC6d
CDoX0hPLxOmfjVV5aTdPaVHJ7RGytuSXOIG+SjgF8xx/g+J9An3CXkCyQHGYdPjS
MSfE22p08+OHRJqpfP/UEr4jvh2kqcfhaagi4D2cp3J+4Z/TZiys760pHGuV4Twt
0tMCdw0J9wOXivBdqfqmfvghNi+3ULBa8nUEXnpGEM5sLmoIeGiLKfdym8JIA2Lv
E6of+HtVgbz+i6UWn5XIspcS9tH+HjoWWoADvtjodJySRezXNGPAuutRJK2eaqa8
rS/8w46N97NTNEXVas1GVDBQOOoe/Mx8OpHZMs0SYAAu8WgBnUALAChivajBCydf
D7k9Js8HRjC3vNLfCiNBgt0iX8gdNoGjDJDB9gT6LJ/oPvcQ2maHkDImHrql6uRM
HC45ILXFuemehcr7lwdOGA==
=/wc0
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Package: docker.io
Version: 17.12.1+dfsg-1
Looks like this bug is a duplicate of #855621 which has been fixed by
building Docker/containerd binaries from the same source package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
