[Buildroot] Docker client does not function correctly in 2018.11

David J. Fogle Dave at exitstrategytech.com
Wed Dec 5 23:51:24 UTC 2018


Skiff build does not function either. Seems to be the same issue, but journalctl catches nothing of the output in the skiff build.


Sent from Samsung Focus


-------- Original message --------
From: "David J. Fogle" <Dave at exitstrategytech.com>
Date: 12/5/18 4:55 PM (GMT-06:00)
To: Christian Stewart <christian at paral.in>
Cc: buildroot at busybox.net, Matthew Weber <matthew.weber at rockwellcollins.com>, Hamilton Southworth <hamilton at aperturerobotics.com>
Subject: Re: Docker client does not function correctly in 2018.11

I am building from the skiff now, will report back in about 20 once the image in on a drive.



David Fogle

CTO - Exit Strategy


-------- Original message --------
From: Christian Stewart <christian at paral.in>
Date: 12/5/18 4:38 PM (GMT-06:00)
To: "David J. Fogle" <Dave at exitstrategytech.com>
Cc: buildroot at busybox.net, Matthew Weber <matthew.weber at rockwellcollins.com>, Hamilton Southworth <hamilton at aperturerobotics.com>
Subject: Re: Docker client does not function correctly in 2018.11

David,

On Wed, Dec 5, 2018, 2:04 PM David J. Fogle <Dave at exitstrategytech.com<mailto:Dave at exitstrategytech.com>> wrote:

I have investigated further, and narrowed the issue down to the containerd, not the client. The containerd is being passed an invalid flag -metrics-interval, and is constantly looping through it's init process.

Thank you for looking into this. We are also aware of a hang in docker startup due to random data starvation.

Could you please try either the "skiff" branch of https://github.com/paralin/buildroot.git or apply this patch: https://patchwork.ozlabs.org/patch/1003677/

There was a commit merged as part of that series to bump containerd to a newer version. However, the docker engine bump from that series did not get merged until after the 2018.11 release window (the series was originally intended to be merged all at once). It's likely there is some incompatibility in startup flags as you say between the two containerd and docker versions present.

I recommend to revert the containerd bump in 2018.11 or backport the docker engine bump.

Best regards,
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181205/86718ac0/attachment-0001.html>


More information about the buildroot mailing list