[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

Thanks for the advice. I have to put my kernel builder hat on for the first time in a while it seems. I have configured the kernel according to the recommended settings in the Gentoo handbook, and am trying again. After a build with overlay enabled, I was able to get docker to run far enough along to complain about cgroup support lacking, so I think that the skiff builds are fixed, I will reply with verification as soon as I download the image from the build server.

Thank you for your help, if you represent even 1 percent of the contributors to buildroot, I imagine this project is worth me investing time into it. So far, this has been an amazing journey.  

-----Original Message-----
From: Christian Stewart <christian at paral.in> 
Sent: Wednesday, December 5, 2018 7:47 PM
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: Re: Docker client does not function correctly in 2018.11

Hi David,

On Wed, Dec 5, 2018 at 5:42 PM David J. Fogle <Dave at exitstrategytech.com> wrote:
> 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?

There is no official documentation at this point, the Docker package exists as a "include the Docker binaries in my target system" minimal option in Buildroot, and developers are currently left to decide how to configure it themselves.

If you want to see how I use Docker and Buildroot as a reference, see https://github.com/paralin/SkiffOS.git - feel free to open issues there as well if you have Docker related questions / other non-Buildroot specific topics to discuss.

The minimal requirements for Docker are a kernel compiled with a specific set of features enabled (see the Docker documentation) as well as some init process to start the daemon at system startup.

Best regards,
Christian Stewart