[BUG] Got HTTP: invalid Host header on cluster create

[moshe-kabala]

What did you do

Clone the repo on a Linux machine run make build and then copy the binary to /usr/local/bin
It works fine when installing it with the install.sh, Maybe the bug related to this bug. I used Go version 1.20.6

• How was the cluster created?

  • k3d cluster create clustername

• What did you do afterwards?
  Just create cluster

What did you expect to happen

Cluster created

Screenshots or terminal output

INFO[0018] Injectig records for hostAliases (incl. host.k3d.internal) and for 2 network members into CoreDNS configmap...
ERROR[0019] Failed Cluster Start: error during post-start cluster preparation: error overwriting contents of /etc/hosts: docker failed to attach to exec process in node 'k3d-clustername-server-0': HTTP: invalid Host header

Which OS & Architecture

Linux Ubunto

• output of k3d runtime-info

arch: x86_64
cgroupdriver: systemd
cgroupversion: "2"
endpoint: /var/run/docker.sock
filesystem: extfs
infoname: tensorleap-OMEN-Laptop
name: docker
os: Ubuntu 22.04.2 LTS
ostype: linux
version: 24.0.4

Which version of k3d

5.5.1 & 5.5.0

• output of k3d version

k3d version v5.5.1
k3s version v1.26.4-k3s1 (default)

Which version of docker

20.10.22

• output of docker version and docker info

docker version
Client: Docker Engine - Community
 Version:           20.10.22
 API version:       1.41
 Go version:        go1.18.9
 Git commit:        3a2c30b
 Built:             Thu Dec 15 22:28:04 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          24.0.4
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.5
  Git commit:       4ffc614
  Built:            Fri Jul  7 14:50:55 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.21
  GitCommit:        3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:          1.1.7
  GitCommit:        v1.1.7-0-g860f061
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.9.1-docker)
  compose: Docker Compose (Docker Inc., v2.19.1)
  scan: Docker Scan (Docker Inc., v0.23.0)

Server:
 Containers: 11
  Running: 10
  Paused: 0
  Stopped: 1
 Images: 34
 Server Version: 24.0.4
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
 runc version: v1.1.7-0-g860f061
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.19.0-46-generic
 Operating System: Ubuntu 22.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 30.99GiB
 Name: tensorleap-OMEN-Laptop
 ID: c0d61a09-4827-4668-bd52-8ead74cc5028
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  [127.0.0.0/8](http://127.0.0.0/8)
 Live Restore Enabled: false

[jan-sykora]

We've encountered the same issue and a workaround was to downgrade from the latest Go 1.20.6 to 1.20.5.

[moshe-kabala]

Docker(moby) release new version that solves this problem, is there any plan for a new release with this version?

[iwilltry42]

Should be fixed in https://github.com/k3d-io/k3d/releases/tag/v5.5.2

[iwilltry42]

Feel free to reopen if the issue persists for you. I couldn't reproduce it after the dependency update 👍