[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

Ok, after adding in overlay, I am closer I think. One more kernel build with cgroup support. Is there any form of official documentation on docker and buildroot, or is it shoot first ask questions later?


Sent from Samsung Focus


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

I'm not seeing that behaviour though, it's the deamon starting, erroring out, then restarting again, a few times a second. Only message anywhere is the one about the invalid flag from the go error output, about -metrics-interval. Last time I ran into something like this was Debian had a mismatch between runc and docker at one point, and it did similar things.



David Fogle

CTO - Exit Strategy


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

Hi David,

Please provide your defconfig, the commit hash you built from (of
Buildroot), and any relevant log files.

On Wed, Dec 5, 2018 at 3:57 PM David J. Fogle <Dave at exitstrategytech.com> wrote:
> This also may be due to a lack of any functional docker filesystem drivers, as aufs patches break when applied, and overlay apparently is not usable either.

We have witnessed this issue already, and in fact, it occurs on my
laptop (Gentoo, latest) during the boot-up phase.

Docker will hang for about a minute or two. If I press keys on my
keyboard sometimes it will start up, but it seems to hang with no log
output for a while.

We looked at an strace before (Matthew and I both) and found the issue
to be related to reading random data from the system at startup. Since
Docker starts at the end of the boot-up phase, it seems that something
in this process is causing Docker to either not have enough random
data available from the system, or encounter some other hang.

Overlay works fine, why is it "apparently not usable?" I have multiple
machines running overlay based filesystems with this version of
Docker, including Raspberry Pis and Odroids (ARM machines). They all
suffer from the sporadic Docker hang on start, however.

Best,
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20181206/bfa036c5/attachment-0001.html>