Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 3/4] package/docker-engine: bump to 19.03.5
Date: Wed, 04 Dec 2019 16:28:46 -0800	[thread overview]
Message-ID: <87immv8vk1.fsf@paral.in> (raw)
In-Reply-To: <871rtkl8xn.fsf@dell.be.48ers.dk>

Hi Peter,

Peter Korsgaard <peter@korsgaard.com> writes:

>>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:
>  >  delete mode 100644 package/docker-engine/0001-Fix-faulty-runc-version-commit-scrape.patch
>
> Next to the text cases pointed out by Thomas, a more detailed commit
> message would be great - E.G. what happened to your patch that you are
> now dropping? Did it get applied upstream? Is it no longer needed? If
> so, why?

It's a really minor patch, I don't think anyone would care really that
it was dropped. I will be sure to mention it in future commit messages
(or if I need to submit a revision for this).

> I don't really understand the relation between containerd and runc, but
> containerd seems to bundle runc? If we backport runc to 2019.02.x do we
> then also need to backport containerd?

The "runc" package in Buildroot compiles the userspace binary "runc"
which is called by "containerd" at runtime to start namespaced processes
(aka containers). "runc" means "run container."

The "runc" version referenced in containerd is the client for the runc
binary and the interfaces between. Matching the expected versions to
each other is necessary but security releases should be compatible.

> According to https://github.com/opencontainers/runc/releases, this is a
> security bump so it should be marked as such and we presumably want to
> backport it to 2019.02.x even though that uses docker 18.09?

Not sure on this one.

Best regards,
Christian

  reply	other threads:[~2019-12-05  0:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  4:50 [Buildroot] [PATCH v1 1/4] package/runc: bump to 1.0.0-rc9 Christian Stewart
2019-12-03  4:50 ` [Buildroot] [PATCH v1 2/4] package/docker-containerd: bump to 1.2.11 Christian Stewart
2019-12-04 10:00   ` Peter Korsgaard
2020-01-05 22:39   ` Peter Korsgaard
2020-01-10 19:44     ` Peter Korsgaard
2019-12-03  4:50 ` [Buildroot] [PATCH v1 3/4] package/docker-engine: bump to 19.03.5 Christian Stewart
2019-12-03  7:57   ` Thomas Petazzoni
2019-12-04  2:18     ` Christian Stewart
2019-12-04  7:52       ` Thomas Petazzoni
2019-12-07 22:50         ` Christian Stewart
2019-12-04  9:46   ` Peter Korsgaard
2019-12-05  0:28     ` Christian Stewart [this message]
2020-01-05 22:39   ` Peter Korsgaard
2020-01-10 19:44     ` Peter Korsgaard
2020-01-10 19:45   ` Peter Korsgaard
2019-12-03  4:50 ` [Buildroot] [PATCH v1 4/4] package/docker-cli: " Christian Stewart
2020-01-05 22:39   ` Peter Korsgaard
2020-01-10 19:45   ` Peter Korsgaard
2019-12-04  9:55 ` [Buildroot] [PATCH v1 1/4] package/runc: bump to 1.0.0-rc9 Peter Korsgaard
2020-01-05 22:38 ` Peter Korsgaard
2020-01-10 19:45 ` Peter Korsgaard

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=87immv8vk1.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