From: codedmart <codedmart@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: `docker build` fails with "ERROR: http: invalid Host header" with docker-buildx-0.10.3_3
Date: Fri, 01 Sep 2023 23:34:03 +0200 [thread overview]
Message-ID: <20230901213403.dL9dc0yzBCPlALvpg_nbR-W7zb6C46ih68gqK7tVkTo@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: 3006 bytes --]
New comment by codedmart on void-packages repository
https://github.com/void-linux/void-packages/issues/45780#issuecomment-1703341259
Comment:
I think I may have just ran into something related to this. I am on a fresh new install and tried setting up a new builder for multiarch with docker buildx.
```
❯ docker buildx create --name mybuilder --driver docker-container --bootstrap
[+] Building 15.6s (1/1) FINISHED
=> ERROR [internal] booting buildkit 15.6s
=> => pulling image moby/buildkit:buildx-stable-1 1.0s
=> => creating container buildx_buildkit_mybuilder0 14.6s
------
> [internal] booting buildkit:
#0 15.58 time="2023-09-01T21:32:10Z" level=warning msg="using host network as the defaultime="2023-09-01T21:32:10Z" level=warning msg="using host network as the default"
#0 15.58 time="2023-09-01T21:32:10Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
#0 15.58 dtime="2023-09-01T21:32:10Z" level=info msg="found 1 workers, default=\"7vqkitbi1mrzlx5y7esqwgsx0\""
#0 15.58 `time="2023-09-01T21:32:10Z" level=warning msg="currently, only the default worker can be used."
#0 15.58 \time="2023-09-01T21:32:10Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
#0 15.58 time="2023-09-01T21:32:10Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
#0 15.58 time="2023-09-01T21:32:10Z" level=warning msg="currently, only the default worker can be used."
#0 15.58 time="2023-09-01T21:32:10Z" level=warning msg="currently, only the default worker can be used."
#0 15.58
------
mybuilder
```
Because then I see:
```
❯ docker buildx ls
NAME/NODE DRIVER/ENDPOINT STATUS BUILDKIT PLATFORMS
mybuilder docker-container
mybuilder0 unix:///var/run/docker.sock error
default * docker-container
default default inactive
Failed to get status for mybuilder (mybuilder0): http: invalid Host header
```
I do not have the previous package to fall back to :frowning_face:.
next prev parent reply other threads:[~2023-09-01 21:34 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 [this message]
2023-09-03 15:01 ` nekopsykose
2023-09-06 8:01 ` [ISSUE] [CLOSED] " etherswangel
2023-09-06 8:01 ` etherswangel
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=20230901213403.dL9dc0yzBCPlALvpg_nbR-W7zb6C46ih68gqK7tVkTo@z \
--to=codedmart@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).