From: Leo Famulari <leo@famulari.name>
To: 34459@debbugs.gnu.org
Subject: bug#34459: Docker and containerd bundled dependencies — what to do?
Date: Tue, 12 Feb 2019 13:03:21 -0500 [thread overview]
Message-ID: <20190212180321.GB14638@jasmine.lan> (raw)
In-Reply-To: <20190212014501.31dcb6a8@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Tue, Feb 12, 2019 at 01:45:01AM +0100, Danny Milosavljevic wrote:
> Docker still contains some vendored dependencies, among those github.com/opencontainers/runc,
> in directory "vendor", and so does containerd. It might make sense to also remove them now.
I didn't do anything regarding the vendored / bundled deps in my patches
related to CVE-2019-5736 <https://bugs.gnu.org/34446>.
Regarding Docker, the update to 18.09.2 ostensibly fixed CVE-2019-5736,
I suppose by updating the bundled copy of runc.
For containerd I didn't change the package at all.
Both Docker and containerd depend on our runc package. If they don't
actually use it but instead use their bundled copy, we should remove the
dependency and document the bundling, or work on unbundling.
Unfortunately this is complicated for us in recent versions of Go:
https://lists.gnu.org/archive/html/guix-devel/2018-11/msg00223.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-02-12 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 23:37 [bug#34446] Runc container escape patches CVE-2019-5736 Leo Famulari
2019-02-12 0:10 ` Danny Milosavljevic
2019-02-12 0:13 ` Danny Milosavljevic
2019-02-12 17:56 ` bug#34446: " Leo Famulari
2019-02-12 0:27 ` [bug#34446] [PATCH 1/2] gnu: runc: Update to 1.0.0-rc6 [fixes CVE-2019-5736] Leo Famulari
2019-02-12 0:27 ` [bug#34446] [PATCH 2/2] gnu: Docker: Update to 18.09.2 Leo Famulari
2019-02-12 0:45 ` [bug#34446] [PATCH 1/2] gnu: runc: Update to 1.0.0-rc6 [fixes CVE-2019-5736] Danny Milosavljevic
2019-02-12 18:03 ` Leo Famulari [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=20190212180321.GB14638@jasmine.lan \
--to=leo@famulari.name \
--cc=34459@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.