FS#50432 - [containerd] startup hangs bad listen address format
Attached to Project:
Arch Linux
Opened by Carsten Pohl (archlinuxuser7719) - Thursday, 18 August 2016, 09:23 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 18 August 2016, 13:37 GMT
Opened by Carsten Pohl (archlinuxuser7719) - Thursday, 18 August 2016, 09:23 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 18 August 2016, 13:37 GMT
|
Details
Description:
With the newest update of containerd, docker (containerd) does not start anymore. The startup hangs, and if you look into journalctl you see: Aug 18 11:00:48 xxxx systemd[1]: Starting Docker Socket for the API. Aug 18 11:00:48 xxxx systemd[1]: Listening on Docker Socket for the API. Aug 18 11:00:48 xxxx systemd[1]: Starting Docker Application Container Engine... Aug 18 11:00:49 xxxx docker[1186]: time="2016-08-18T11:00:49.087804438+02:00" level=info msg="New containerd process, pid: 1214\n" Aug 18 11:00:49 xxxx docker[1186]: time="2016-08-18T11:00:49.122544849+02:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/ Aug 18 11:00:55 xxxx docker[1186]: time="2016-08-18T11:00:55.092126344+02:00" level=info msg="New containerd process, pid: 1229\n" Aug 18 11:00:55 xxxx docker[1186]: time="2016-08-18T11:00:55.103697145+02:00" level=fatal msg="bad listen address format /var/run/docker/libcontainerd/ Additional info: * package version [2016-08-18 10:12] [ALPM] upgraded containerd (0.2.2-1 -> 0.2.3-1) Steps to reproduce: sudo systemctl start docker journalctl |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 18 August 2016, 13:37 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#50430
Thursday, 18 August 2016, 13:37 GMT
Reason for closing: Duplicate
Additional comments about closing:
To make matters worse, i cant delete my own reported bug. Sorry for the inconvenience.
https://bugs.archlinux.org/task/50430