On 21 Feb 2017, at 7:48 AM, Samuel Thibault <sthiba...@debian.org> wrote: > > Samuel Thibault, on lun. 20 févr. 2017 21:37:11 +0100, wrote: >> Samuel Thibault, on lun. 20 févr. 2017 21:30:58 +0100, wrote: >>> 2017-02-20T21:29:05.031246+01:00 var docker[4807]: >>> time="2017-02-20T21:29:05.030971938+01:00" level=info msg="New containerd >>> process, pid: 4822\n" >>> 2017-02-20T21:29:05.046488+01:00 var docker[4807]: >>> time="2017-02-20T21:29:05.046388294+01:00" level=fatal msg="bad listen >>> address format /var/run/docker/libcontainerd/docker-containerd.sock, >>> expected proto://address" >> >> I found this: >> >> https://patrick.georgi.family/2017/02/18/bad-listen-address-format-docker-error-on-debian-and-elsewhere/ >> >> which I'll use as workaround (it seems to work fine here), > > I spoke too fast, I'm getting other incompatibilities. I had to > downgrade containerd.
Hi Samuel. I'm afraid I messed up by uploading containerd, libnetwork and runc to unstable and the appropriate Docker version (1.13) to experimental which is why you are seeing this problem. Next time I'll make sure to upload all four packages to the same place. I've just re-uploaded containerd, libnetwork and runc with Breaks lines in place to ensure that this doesn't happen during the 1.13 upload process. As you mention downgrading fixes things. You might like to also downgrade runc and libnetwork just to be safe. Regards, Tim.
signature.asc
Description: Message signed with OpenPGP using GPGMail
