From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15754] New: The docker-engine and docker-cli versions are not compatible with go 1.19.12 version
Date: Mon, 04 Sep 2023 13:36:19 +0000 [thread overview]
Message-ID: <bug-15754-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15754
Bug ID: 15754
Summary: The docker-engine and docker-cli versions are not
compatible with go 1.19.12 version
Product: buildroot
Version: 2023.02.4
Hardware: All
OS: Linux
Status: NEW
Severity: critical
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: dominique.tronche@eviden.com
CC: buildroot@uclibc.org
Target Milestone: ---
In 2023.02.4, go package has been upgraded to v1.19.12, however docker packages
version is still an unpatched 23.0.5
Hence docker containers face the bug corrected in 24.0.5 in master branch (see
commit a9cd24738a7) which produces "invalid Host header" error message
Either docker version should be upgraded to a version compatible with go
1.19.12 in LTS 2023.02 or the patches from christian@aperture.us should be
introduced (the patch for docker-cli does not work as the versions in
vendor.mod are not correct)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-09-04 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 13:36 bugzilla [this message]
2023-09-05 7:16 ` [Buildroot] [Bug 15754] The docker-engine and docker-cli versions are not compatible with go 1.19.12 version bugzilla
2023-09-06 19:09 ` bugzilla
2023-09-07 9:19 ` bugzilla
2023-09-13 20:23 ` bugzilla
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=bug-15754-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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