From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/9] upgrade docker-engine and associated components
Date: Thu, 01 Mar 2018 19:15:07 +0100 [thread overview]
Message-ID: <87371jirx0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <874llzr8at.fsf@paral.in> (Christian Stewart's message of "Thu, 01 Mar 2018 12:54:02 -0500")
>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:
> Hi Peter,
> Peter Korsgaard <peter@korsgaard.com> writes:
>> > - runc to 9f9c96235cc97674e935002fc3d78361b696a69e
>> > - docker-containerd to v1.0.2
>> > - docker-engine to v2018.03.0-ce-rc1
>>
>> I am far from a docker expert, but isn't this an 'edge' release? Given
>> the Buildroot release schedule, wouldn't it make more sense to use the
>> 'stable' releases with a similar quarterly support/release schedule?
> Yes, it's intended to be merged into "next" for release not in Buildroot
> 2018.02 but later. I thought I had mentioned that in the cover letter,
> but I guess that was in another revision, lost somewhere months ago.
> The reason is because from our testing on various devices with varying
> container workloads, the only two stable versions (with no critical
> bugs) of Docker that we have been able to find were early 2017 or 2018.03-rc1.
That sounds pretty horrible :/
> 2018.03-rc1 will be released as a full release soon as 2018.02 was
> completely unusable due to a "container already exists" error when
> trying to start a container.
> If you would like me to make another series based around 17.12.1-ce that
> was just released, I would be happy to do so.
Well, only if it actually works. But if you think there will be a new
(working) stable release before our next release (E.G. by April) then
I'm also fine with going with this 2018.03 version.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-03-01 18:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 7:20 [Buildroot] [PATCH v2 0/9] upgrade docker-engine and associated components Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 1/9] tini: new package Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 2/9] dumb-init: " Christian Stewart
2018-03-01 9:02 ` Thomas Petazzoni
2018-03-01 15:51 ` Peter Korsgaard
2018-03-01 16:08 ` Thomas Petazzoni
2018-03-01 17:21 ` Peter Korsgaard
2018-03-01 22:04 ` Thomas Petazzoni
2018-03-01 22:23 ` Yann E. MORIN
2018-03-01 23:02 ` Baruch Siach
2018-03-03 22:10 ` Yann E. MORIN
2018-03-01 22:32 ` Peter Korsgaard
2018-03-01 17:58 ` Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 3/9] docker-engine: add support for init processes Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 4/9] docker-engine: select static for tini and dumb-init Christian Stewart
2018-03-01 8:59 ` Thomas Petazzoni
2018-03-01 15:52 ` Peter Korsgaard
2018-03-01 17:59 ` Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 5/9] docker-proxy: new package Christian Stewart
2018-03-30 21:30 ` Peter Korsgaard
2018-03-01 7:20 ` [Buildroot] [PATCH v2 6/9] docker-engine: add dependency on docker-proxy Christian Stewart
2018-03-30 21:30 ` Peter Korsgaard
2018-03-01 7:20 ` [Buildroot] [PATCH v2 7/9] runc: bump to 9f9c96235cc Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 8/9] docker-containerd: bump to v1.0.2 Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 9/9] docker-engine: bump to v18.03.0-ce-rc1 Christian Stewart
2018-03-01 10:15 ` [Buildroot] [PATCH v2 0/9] upgrade docker-engine and associated components Peter Korsgaard
2018-03-01 17:54 ` Christian Stewart
2018-03-01 18:15 ` Peter Korsgaard [this message]
2018-03-01 19:06 ` Christian Stewart
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=87371jirx0.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 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.