Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 606170 - =app-emulation/docker-1.11.0 throws bad listen address format with =app-emulation/containerd-0.2.5
Summary: =app-emulation/docker-1.11.0 throws bad listen address format with =app-emula...
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Tianon
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-18 09:56 UTC by Shiba
Modified: 2017-01-27 21:20 UTC (History)
7 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shiba 2017-01-18 09:56:36 UTC
This is what I get in /var/log/docker.log

time="2017-01-18T10:19:21.909240573+01:00" level=info msg="New containerd process, pid: 904\n" 
time="2017-01-18T10:19:21.996456564+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:19:27.911226617+01:00" level=info msg="New containerd process, pid: 939\n" 
time="2017-01-18T10:19:27.925344096+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:19:36.840216339+01:00" level=info msg="New containerd process, pid: 967\n" 
time="2017-01-18T10:19:36.85425638+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:19:43.308858909+01:00" level=info msg="New containerd process, pid: 994\n" 
time="2017-01-18T10:19:43.323368156+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:19:55.701314556+01:00" level=info msg="New containerd process, pid: 1129\n" 
time="2017-01-18T10:19:55.740238963+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:20:11.155384637+01:00" level=info msg="New containerd process, pid: 1237\n" 
time="2017-01-18T10:20:11.169780553+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:20:24.958398281+01:00" level=info msg="New containerd process, pid: 1416\n" 
time="2017-01-18T10:20:24.972097093+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:20:30.960250587+01:00" level=info msg="New containerd process, pid: 1458\n" 
time="2017-01-18T10:20:30.974335932+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:20:40.552683080+01:00" level=info msg="New containerd process, pid: 1487\n" 
time="2017-01-18T10:20:40.567396204+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:20:46.868688783+01:00" level=info msg="New containerd process, pid: 1500\n" 
time="2017-01-18T10:20:46.883151843+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:20:58.002182819+01:00" level=info msg="New containerd process, pid: 1605\n" 
time="2017-01-18T10:20:58.016146843+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:21:12.810528171+01:00" level=info msg="New containerd process, pid: 1639\n" 
time="2017-01-18T10:21:12.825378799+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:21:35.430642860+01:00" level=info msg="New containerd process, pid: 1658\n" 
time="2017-01-18T10:21:35.444957773+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:22:16.278858981+01:00" level=info msg="New containerd process, pid: 1682\n" 
time="2017-01-18T10:22:16.29309571+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:23:19.824036555+01:00" level=info msg="New containerd process, pid: 1739\n" 
time="2017-01-18T10:23:19.837961039+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-18T10:25:17.517766411+01:00" level=info msg="New containerd process, pid: 1783\n" 
time="2017-01-18T10:25:17.532381979+01:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address"

I think it is related to https://github.com/docker/docker/issues/22670 and docker 1.12 should solve the issue. I'm rebuilding my kernel and docker 1.12 to see if this really is the case.

Reproducible: Always
Comment 1 Shiba 2017-01-18 10:47:56 UTC
I can now confirm that =app-emulation/docker-1.12.6 works fine.
Comment 2 kballou 2017-01-18 16:45:56 UTC
I was also seeing the described behaviour and I also saw the issue fixed by (unmasking and) upgrading to =app-emulation/docker-1.12.6.
Comment 3 Stijn Tintel 2017-01-19 21:24:51 UTC
I can confirm this bug. Arch bugtracker has a fix: https://bugs.archlinux.org/task/50430
Comment 4 Emmanuel Rosa 2017-01-21 03:03:33 UTC
Yep, same problem here. I have Docker 1.11.0 and containerd 0.2.5

Any attempt to use the docker client (ex. docker version) just causes the client to hang.

time="2017-01-20T21:35:11.234318333-05:00" level=info msg="New containerd proces
s, pid: 3691\n" 
time="2017-01-20T21:35:11.318353741-05:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-20T21:35:17.410344498-05:00" level=info msg="New containerd process, pid: 3833\n" 
time="2017-01-20T21:35:17.421186376-05:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-20T21:35:33.341629498-05:00" level=info msg="New containerd process, pid: 4244\n" 
time="2017-01-20T21:35:33.353068123-05:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-20T21:38:58.782413934-05:00" level=info msg="New containerd process, pid: 5437\n" 
time="2017-01-20T21:38:58.793409943-05:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-20T21:39:04.784006193-05:00" level=info msg="New containerd process, pid: 5444\n" 
time="2017-01-20T21:39:04.795747535-05:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-20T21:39:45.979901308-05:00" level=info msg="New containerd process, pid: 5466\n" 
time="2017-01-20T21:39:45.9908606-05:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-20T21:40:17.090515759-05:00" level=info msg="New containerd process, pid: 7833\n" 
time="2017-01-20T21:40:17.108412933-05:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address" 
time="2017-01-20T21:40:58.928286139-05:00" level=info msg="New containerd process, pid: 9385\n" 
time="2017-01-20T21:40:58.93922472-05:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address"
Comment 5 Emmanuel Rosa 2017-01-21 03:22:35 UTC
My solution was to downgrade containerd to 0.2.0, which also downgrades runc from 1.0.0-rc2 to 0.1.0.
Comment 6 Bruno Pinto 2017-01-27 21:18:22 UTC
Docker 1.12 is stable and docker 1.11 has been removed. I think we can close this now?
Comment 7 Manuel Rüger (RETIRED) gentoo-dev 2017-01-27 21:20:36 UTC
Please test again with docker 1.12.6