From: etherswangel <etherswangel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] `docker build` fails with "ERROR: http: invalid Host header" with docker-buildx-0.10.3_3
Date: Wed, 06 Sep 2023 10:01:31 +0200 [thread overview]
Message-ID: <20230906080131.RONW-9PHVHTMBo6xBZOq9yfDDh2-5_bimMqqLmPcv2A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45780@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Closed issue by etherswangel on void-packages repository
https://github.com/void-linux/void-packages/issues/45780
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64 AuthenticAMD notuptodate DFFF
### Package(s) Affected
docker-buildx-0.10.3_3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/moby/moby/issues/45935
### Expected behaviour
work with
```
docker-24.0.5_2
docker-cli-24.0.5_2
moby-24.0.5_2
```
and lower versions (tested 24.0.5_1)
### Actual behaviour
"ERROR: http: invalid Host header" when building
downgrade to docker-buildx-0.10.3_2 solves the issue. (docker-buildx-0.10.3_2 works with docker-24.0.5_2 and moby-24.0.5_2, but docker-buildx-0.10.3_3 doesn't)
### Steps to reproduce
1. `xbps-install -S docker-buildx-0.10.3_3`
2. `docker build .` fails
3. `xdowngrade /var/cache/xbps/docker-buildx-0.10.3_2.x86_64.xbps`
4. `docker build .` is fine
"FROM node:18-alpine" is the only line in Dockerfile
prev parent reply other threads:[~2023-09-06 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 14:06 [ISSUE] " etherswangel
2023-09-01 21:34 ` codedmart
2023-09-03 15:01 ` nekopsykose
2023-09-06 8:01 ` etherswangel
2023-09-06 8:01 ` etherswangel [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=20230906080131.RONW-9PHVHTMBo6xBZOq9yfDDh2-5_bimMqqLmPcv2A@z \
--to=etherswangel@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).