FS#50430 - [docker] docker 1.11 doesn't start with containerd 0.2.3-1

Attached to Project: Community Packages
Opened by Yoan Blanc (greut) - Thursday, 18 August 2016, 05:34 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 19 August 2016, 12:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 14
Private No

Details

Description:

After this morning's upgrade, the docker daemon doesn't seem to start. After enabling the --debug mode, it complains about the listen address format. Downgrading to 0.2.2-1 fixed it.


Additional info:
* 0.2.3-1
* bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address

Steps to reproduce:

* Upgrade containerd
* Restart docker
* See that it hangs...

Cheers!
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Friday, 19 August 2016, 12:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.12.1-1
Comment by Vic Luo (htfy96) - Thursday, 18 August 2016, 06:06 GMT
Confirmed on my docker 1.11-2 with containerd 0.2.3-1.

Similar bug reports are found at https://github.com/docker/docker/issues/22950 . It seems that this bug has been fixed in https://github.com/docker/docker/commit/6889c3276c6895a8440dc8883b8cd608793199f3 as part of docker 1.12.
Comment by Ike Devolder (BlackEagle) - Thursday, 18 August 2016, 08:25 GMT
https://github.com/docker/containerd/issues/299
https://github.com/docker/docker/issues/23289

Or we must downgrade containerd, or we must update docker to 1.12
Comment by Giovanni Condello (nanomad) - Thursday, 18 August 2016, 08:25 GMT
I've back-ported the patch to the 1.11.2 release of docker and successfully tested it locally. I've attached it here
Comment by Giovanni Condello (nanomad) - Thursday, 18 August 2016, 08:36 GMT
(Forget that, i was looking at the wrong commit)
Comment by Giovanni Condello (nanomad) - Thursday, 18 August 2016, 08:48 GMT
Actually, I'm having all kind of issues with 1.11.2 and containerd 0.2.3 even after the patch so I guess it's better to wait for the new docker and downgrade in the meantime....
Comment by Nils (Eka) - Thursday, 18 August 2016, 09:06 GMT
I can confirm the issue this morning.
Comment by James Schorr (jschorr) - Thursday, 18 August 2016, 16:05 GMT
I've had the same issue this morning as well. Downgrading containerd to 0.2.2-1 and docker all the way back to 1.1.10-3-1 worked for me. I initially tried a couple of the 1.1.11 versions but kept getting image building issues.
Comment by Skyler Hawthorne (dead10ck) - Thursday, 18 August 2016, 18:17 GMT
Confirming this issue.
Comment by Mike Javorski (javmorin) - Thursday, 18 August 2016, 19:10 GMT
The official docker releases bundle specific (and vendored with "docker-" prefix) versions of the runc and containerd software. The runc and containerd Arch packages being used with the docker Arch package are not always the specified versions and thus can cause incompatibility.

For those interested in testing docker 1.12 (or just wanting to get docker running again) I have pushed a docker-bin PKGBUILD to AUR. This uses the official binary set + all the supporting bits that are included in the regular docker Arch package. I have also posted a feature request (FS #50436) asking that the main docker package be updated to build and bundle the specific runc and containerd versions to prevent these issues in the future.
Comment by Sébastien Luttringer (seblu) - Thursday, 18 August 2016, 22:19 GMT
I'm on it
Comment by Sébastien Luttringer (seblu) - Friday, 19 August 2016, 00:12 GMT
I changed the PKGBUILD to build runc and containerd based on the commit version in the Dockerfile as pointed here: https://github.com/docker/containerd/issues/299#issuecomment-240745119

So far, the 1.12.1 version is working on my machines.

Comment by Yoan Blanc (greut) - Friday, 19 August 2016, 06:48 GMT
@seblu

Upgrading docker to 1.12.1, and uninstalling runc and containerd made it for me. Thanks!
Comment by Mike Javorski (javmorin) - Friday, 19 August 2016, 07:10 GMT
FYI: The runc and containerd packages should not conflict with the docker packaged ones, but if you aren't using that software independently there is no need to keep them installed.

Thanks @seblu for updating the package so quickly!
Comment by Alexandre MOOTASSEM (amoot) - Friday, 19 August 2016, 10:31 GMT
Thanks @seblu, updated package 1.12.1-1 works great on my envs.

Loading...