From: Dan Walkes <danwalkes@trellis-logic.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: dunfell docker builds broken after go CVE-2023-29406
Date: Sun, 29 Oct 2023 19:36:38 -0600 [thread overview]
Message-ID: <CAAhKrJ3FEs2Fo0D0gY3UNRMZ4tm3gR5L2-7jMtckWgoviJCwSg@mail.gmail.com> (raw)
Hi Everyone,
I've noticed that dunfell docker-ce builds are broken with the latest
poky dunfell branch when testing with tegra. Full details at [1].
Attempts to start any container fail with `http:invalid Host header`
I see a relevant discussion at [2] which mentions docker 19.03 from
the dunfell branch no longer being maintained, so it seems unlikely
the fix at [3] will be backported.
I have a workaround for the time being to revert the patch at [4] in
poky but I'm wondering if there's any better suggestion/option for
dealing with this on the dunfell branch.
Thank you,
Dan Walkes
1: https://github.com/OE4T/tegra-demo-distro/issues/277
2: https://lists.yoctoproject.org/g/meta-virtualization/message/8184
3: https://github.com/docker/cli/issues/4437#issuecomment-1637715017
4: https://github.com/yoctoproject/poky/commit/f7f7d5514cf0f63a34d1c75efb031829808ddf2e
next reply other threads:[~2023-10-30 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 1:36 Dan Walkes [this message]
2023-10-30 2:46 ` [meta-virtualization] dunfell docker builds broken after go CVE-2023-29406 Bruce Ashfield
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=CAAhKrJ3FEs2Fo0D0gY3UNRMZ4tm3gR5L2-7jMtckWgoviJCwSg@mail.gmail.com \
--to=danwalkes@trellis-logic.com \
--cc=meta-virtualization@lists.yoctoproject.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).