go 1.20.6: failed to attach to exec: http: invalid Host header

[earl-warren]

Bug report info

When compiled with go 1.20.6 ACT will fail with:


TRAC[2023-07-12T10:51:41+02:00] Working directory '/workspace/root/tet'       dryrun=false job=/test jobID=test matrix="map[]" stage=Main step="echo All Goodaa" stepID="[0]" stepNumber=0
[/test] [DEBUG] Working directory '/workspace/root/tet'
TRAC[2023-07-12T10:51:41+02:00]   ❌  Failure - Main echo All Goodaa           dryrun=false job=/test jobID=test matrix="map[]" stage=Main step="echo All Goodaa" stepID="[0]" stepNumber=0 stepResult=failure
[/test]   ❌  Failure - Main echo All Goodaa
TRAC[2023-07-12T10:51:41+02:00] failed to attach to exec: http: invalid Host header  dryrun=false job=/test jobID=test matrix="map[]" stage=Main step="echo All Goodaa" stepID="[0]" stepNumber=0
[/test] failed to attach to exec: http: invalid Host header
TRAC[2023-07-12T10:51:41+02:00] Cleaning up services for job test             dryrun=false job=/test jobID=test matrix="map[]"

golang/go#61076

### Command used with act

```sh
All workflows will do that.

Describe issue

Link to GitHub repository

No response

Workflow content

on: [push]
jobs:
  test:
    runs-on: docker
    steps:
      - run: echo All Good

### Relevant log output

```sh
-

Additional information

No response

[ChristopherHX]

Bug of dependency github.com/docker/docker.

-P docker=-self-hosted is working by not using that package.

• Golang client fails to attach to streams with "http: invalid Host header" with go1.20.6, go1.19.11 moby/moby#45935
• [Bug]: go 1.20.6: "http: invalid Host header, host port waiting failed" testcontainers/testcontainers-go#1359 (even if it is not opened in the repository with the bug)

[ChristopherHX]

I have injected a patch into this PR from docker/cli 4810f69 (using a prerelease of docker/docker)

[metaory]

Hi @ChristopherHX I'm facing the same issue,
given that the issue closed and there a fix commit, is there anything I should be doing to get around this?

[metaory]

my bad, the AUR package is old (v0.2.48-1), the latest release v0.2.49 don't seem to have the issue 👍