All of lore.kernel.org
 help / color / mirror / Atom feed
From: David J. Fogle <Dave@exitstrategytech.com>
To: buildroot@busybox.net
Subject: [Buildroot] Docker client does not function correctly in 2018.11
Date: Fri, 7 Dec 2018 16:19:04 +0000	[thread overview]
Message-ID: <607d909eed104898b2e059e0326a4415@exitstrategytech.com> (raw)
In-Reply-To: <ff88c64bc71a4a3e816cf4c90a501ec3@exitstrategytech.com>

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>

  reply	other threads:[~2018-12-07 16:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 17:31 [Buildroot] Docker client does not function correctly in 2018.11 David J. Fogle
2018-12-05 22:03 ` David J. Fogle
2018-12-05 22:39   ` Christian Stewart
2018-12-05 22:55     ` David J. Fogle
2018-12-05 23:51       ` David J. Fogle
2018-12-05 23:56       ` David J. Fogle
2018-12-06  0:37         ` Christian Stewart
2018-12-06  0:38           ` David J. Fogle
2018-12-06  0:41           ` David J. Fogle
2018-12-06  1:41             ` David J. Fogle
2018-12-06  1:47               ` Christian Stewart
2018-12-06  2:16                 ` David J. Fogle
2018-12-06  2:23                   ` Christian Stewart
2018-12-06  2:24                     ` David J. Fogle
2018-12-06  2:36                       ` David J. Fogle
2018-12-07 16:19                         ` David J. Fogle [this message]
2018-12-16 14:13                           ` Peter Korsgaard
2018-12-06  8:49                 ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=607d909eed104898b2e059e0326a4415@exitstrategytech.com \
    --to=dave@exitstrategytech.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.