-
Notifications
You must be signed in to change notification settings - Fork 18.3k
Closed
Labels
NeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.telemetryx/telemetry issuesx/telemetry issues
Milestone
Description
Go version
go version 1.23.0 linux/arm64
Output of go env
in your module/workspace:
I'm unable to provide the output of `go env` as it fails with the same telemetry fork/exec error.
What did you do?
Our automated image build process fails to perform any step that invokes the go
binary with the following error:
can't start telemetry child process: fork/exec /usr/local/go/bin/go: invalid argument
The Dockerfile is here, and is being built via a script that invokes docker buildx
with multiple platforms, like:
docker buildx build --platform=linux/amd64,linux/arm64 --file 1.23/Dockerfile
It seems that there is something inherent in the qemu arm64 environment that renders go
unable to fork itself to complete the telemetry setup. I'm fairly confident it's something specific to the 1.23 release as 1.22.6 builds successfully using the same setup today.
What did you see happen?
Failures to invoke any go
command
What did you expect to see?
A successful install and configuration of go 1.23.0 in a multi-arch docker build.
TanZng, zaki-arain, jpo-tu, nirui, kotaroyamazaki and 10 moreBuckarooBanzay
Metadata
Metadata
Assignees
Labels
NeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.telemetryx/telemetry issuesx/telemetry issues