From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Docker client does not function correctly in 2018.11
Date: Sun, 16 Dec 2018 15:13:38 +0100 [thread overview]
Message-ID: <877eg9blv1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <607d909eed104898b2e059e0326a4415@exitstrategytech.com> (David J. Fogle's message of "Fri, 7 Dec 2018 16:19:04 +0000")
>>>>> "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
next prev parent reply other threads:[~2018-12-16 14:13 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
2018-12-16 14:13 ` Peter Korsgaard [this message]
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=877eg9blv1.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox