From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/docker-containerd: bump to 1.3.2
Date: Tue, 04 Feb 2020 15:02:04 -0800 [thread overview]
Message-ID: <874kw6gdn7.fsf@paral.in> (raw)
In-Reply-To: <CA+h8R2puYbJDhqUzYzxfyqV9DzBPwHDyUgxa42y5QFoUT=QrRw@mail.gmail.com>
Hi Peter, all,
Christian Stewart <christian@paral.in> writes:
>> Can you provide a more detailed commit message, please?
>>
>> In the past we have matched the runc and containerd versions with what
>> upstream uses for docker-ce.
>>
>> What does this bring when used with docker-engine 19.03? Is it
>> compatible?
While this release (1.3.x) is compatible with Docker and containerd is a
separate project now (and could be updated as releases are published,
independently from Docker);
Docker 19.03.4 bumped their containerd reference to 1.2.10. Containerd
has released a 1.2.12 release (on the 1.2.x as opposed to 1.3.x series)
with bugfixes.
For now, I will withdraw this patch and re-submit one to bump to 1.2.12.
Best regards,
Christian
prev parent reply other threads:[~2020-02-04 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 4:50 [Buildroot] [PATCH 1/2] package/docker-containerd: bump to 1.3.2 Christian Stewart
2020-01-10 4:50 ` [Buildroot] [PATCH 2/2] package/docker-proxy: bump to feeff4 Christian Stewart
2020-01-10 8:40 ` Peter Korsgaard
2020-01-11 4:20 ` Christian Stewart
2020-01-11 8:31 ` Peter Korsgaard
2020-02-04 23:06 ` Christian Stewart
2020-01-10 8:39 ` [Buildroot] [PATCH 1/2] package/docker-containerd: bump to 1.3.2 Peter Korsgaard
2020-01-11 4:21 ` Christian Stewart
2020-02-04 23:02 ` Christian Stewart [this message]
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=874kw6gdn7.fsf@paral.in \
--to=christian@paral.in \
--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