[Buildroot] Docker client does not function correctly in 2018.11

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

Hello,


I am having a time getting Docker cli to work properly. When executed, as root or use, in busybox or bash, tty or SSH, the same result presents: a flashing cursor on the terminal. Is there somewhere that I can glean some info to debug with? Maybe a hint of where to look?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181205/ca1e4625/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

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.

________________________________
From: buildroot <buildroot-bounces@busybox.net> on behalf of David J. Fogle <Dave@exitstrategytech.com>
Sent: Wednesday, December 5, 2018 11:31:29 AM
To: christian at paral.in
Cc: buildroot at busybox.net
Subject: [Buildroot] Docker client does not function correctly in 2018.11


Hello,


I am having a time getting Docker cli to work properly. When executed, as root or use, in busybox or bash, tty or SSH, the same result presents: a flashing cursor on the terminal. Is there somewhere that I can glean some info to debug with? Maybe a hint of where to look?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181205/42723344/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[Christian Stewart]

David,

On Wed, Dec 5, 2018, 2:04 PM David J. Fogle <Dave@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/84b56138/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

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@paral.in>
Date: 12/5/18 4:38 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: buildroot at busybox.net, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@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/afdfcaf1/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

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@exitstrategytech.com>
Date: 12/5/18 4:55 PM (GMT-06:00)
To: Christian Stewart <christian@paral.in>
Cc: buildroot at busybox.net, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@paral.in>
Date: 12/5/18 4:38 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: buildroot at busybox.net, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@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>

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

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.


Sent from Samsung Focus


-------- Original message --------
From: "David J. Fogle" <Dave@exitstrategytech.com>
Date: 12/5/18 4:55 PM (GMT-06:00)
To: Christian Stewart <christian@paral.in>
Cc: buildroot at busybox.net, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@paral.in>
Date: 12/5/18 4:38 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: buildroot at busybox.net, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@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/875bf1c3/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[Christian Stewart]

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@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

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

I didn't have it enabled on the kernel config, I had assumed it was more or less a default, but it isn't. I am downloading my new build now, then picking up my other half, and I can report back after that. ETA 1 hr.



David Fogle

CTO - Exit Strategy


-------- Original message --------
From: Christian Stewart <christian@paral.in>
Date: 12/5/18 6:36 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: Christian Stewart <christian@paral.in>, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@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.busybox.net/pipermail/buildroot/attachments/20181206/b67c451b/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

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@paral.in>
Date: 12/5/18 6:36 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: Christian Stewart <christian@paral.in>, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@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.busybox.net/pipermail/buildroot/attachments/20181206/0f8ed036/attachment.html>

[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@exitstrategytech.com>
Date: 12/5/18 6:41 PM (GMT-06:00)
To: Christian Stewart <christian@paral.in>
Cc: Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@paral.in>
Date: 12/5/18 6:36 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: Christian Stewart <christian@paral.in>, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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@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.busybox.net/pipermail/buildroot/attachments/20181206/bfa036c5/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[Christian Stewart]

Hi David,

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

[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@paral.in> 
Sent: Wednesday, December 5, 2018 7:47 PM
To: David J. Fogle <Dave@exitstrategytech.com>
Cc: Christian Stewart <christian@paral.in>; Matthew Weber <matthew.weber@rockwellcollins.com>; Hamilton Southworth <hamilton@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@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

[Buildroot] Docker client does not function correctly in 2018.11

[Christian Stewart]

Hi David,

On Wed, Dec 5, 2018 at 6:18 PM David J. Fogle <Dave@exitstrategytech.com> wrote:
> I was able to get docker to run far enough along to complain about cgroup support lacking

The Docker developers created a script to check a kernel .config file
for the required options, you may find it useful.

https://github.com/docker/engine/blob/master/contrib/check-config.sh

Best regards,
Christian

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

Well, as of now, I can start the docker-containerd without any flags, from the cli, and it works. The system unit hangs without output though.



David Fogle

CTO - Exit Strategy


-------- Original message --------
From: Christian Stewart <christian@paral.in>
Date: 12/5/18 8:22 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: Christian Stewart <christian@paral.in>, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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 6:18 PM David J. Fogle <Dave@exitstrategytech.com> wrote:
> I was able to get docker to run far enough along to complain about cgroup support lacking

The Docker developers created a script to check a kernel .config file
for the required options, you may find it useful.

https://github.com/docker/engine/blob/master/contrib/check-config.sh

Best regards,
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181206/2ecfcc8a/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

I think I have myself mostly sorted, I will try to replicate this working config in the morning on 2018.11 , but as far as I can tell, my original issue of the flag being passed when not defined is resolved in your skiff build. I assume your skiff isn't recommended for production use?

From: David J. Fogle <Dave@exitstrategytech.com>
Sent: Wednesday, December 5, 2018 8:24 PM
To: Christian Stewart <christian@paral.in>
Cc: Matthew Weber <matthew.weber@rockwellcollins.com>; Hamilton Southworth <hamilton@aperturerobotics.com>; buildroot at busybox.net
Subject: Re: Re: Re: Docker client does not function correctly in 2018.11

Well, as of now, I can start the docker-containerd without any flags, from the cli, and it works. The system unit hangs without output though.



David Fogle

CTO - Exit Strategy


-------- Original message --------
From: Christian Stewart <christian@paral.in>
Date: 12/5/18 8:22 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: Christian Stewart <christian@paral.in>, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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 6:18 PM David J. Fogle <Dave@exitstrategytech.com> wrote:
> I was able to get docker to run far enough along to complain about cgroup support lacking

The Docker developers created a script to check a kernel .config file
for the required options, you may find it useful.

https://github.com/docker/engine/blob/master/contrib/check-config.sh

Best regards,
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181206/4d757487/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[David J. Fogle]

I have replicated the working configuration from Christian's skiff branch for his SkiffOS into 2018.11, and the issue is 100% a version mismatch in the docker components. Backporting the docker versions from his build into 2018.11 should be sufficient to resolve the issues. Is this something that I can assist in? If so, how would I go about it?

________________________________
From: David J. Fogle
Sent: Wednesday, December 5, 2018 8:36:06 PM
To: Christian Stewart
Cc: Matthew Weber; Hamilton Southworth; buildroot at busybox.net
Subject: RE: Re: Re: Docker client does not function correctly in 2018.11

I think I have myself mostly sorted, I will try to replicate this working config in the morning on 2018.11 , but as far as I can tell, my original issue of the flag being passed when not defined is resolved in your skiff build. I assume your skiff isn?t recommended for production use?

From: David J. Fogle <Dave@exitstrategytech.com>
Sent: Wednesday, December 5, 2018 8:24 PM
To: Christian Stewart <christian@paral.in>
Cc: Matthew Weber <matthew.weber@rockwellcollins.com>; Hamilton Southworth <hamilton@aperturerobotics.com>; buildroot at busybox.net
Subject: Re: Re: Re: Docker client does not function correctly in 2018.11

Well, as of now, I can start the docker-containerd without any flags, from the cli, and it works. The system unit hangs without output though.



David Fogle

CTO - Exit Strategy


-------- Original message --------
From: Christian Stewart <christian@paral.in>
Date: 12/5/18 8:22 PM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: Christian Stewart <christian@paral.in>, Matthew Weber <matthew.weber@rockwellcollins.com>, Hamilton Southworth <hamilton@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 6:18 PM David J. Fogle <Dave@exitstrategytech.com> wrote:
> I was able to get docker to run far enough along to complain about cgroup support lacking

The Docker developers created a script to check a kernel .config file
for the required options, you may find it useful.

https://github.com/docker/engine/blob/master/contrib/check-config.sh

Best regards,
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181207/6f1c4678/attachment.html>

[Buildroot] Docker client does not function correctly in 2018.11

[Peter Korsgaard]

>>>>> "David" == David J Fogle <Dave@exitstrategytech.com> writes:

 > I have replicated the working configuration from Christian's skiff
 > branch for his SkiffOS into 2018.11, and the issue is 100% a version
 > mismatch in the docker components. Backporting the docker versions
 > from his build into 2018.11 should be sufficient to resolve the
 > issues. Is this something that I can assist in? If so, how would I go
 > about it?

I can reproduce it here as well. I have backported commit de336584d255bc
(package/docker-engine: split docker-{cli, engine}, bump to v18.09.0) to
2018.11.x, which fixes the issue for me.

This is be included in the upcoming 2018.11.1 release.

-- 
Bye, Peter Korsgaard

[Buildroot] Docker client does not function correctly in 2018.11

[Thomas Petazzoni]

Hello,

On Wed, 5 Dec 2018 17:47:05 -0800, Christian Stewart wrote:

> 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.

Perhaps we could try to improve things a little bit so that it works
better out of the box ?

If some kernel options are really absolutely needed for Docker to work,
then maybe we should make sure they are enabled: linux/linux.mk already
does that for a few packages.

Alternatively (or additionally), we can add a
package/docker-engine/docker-engine.txt file that gives some
details/suggestions on how to setup Docker in Buildroot.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com