We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
Docker multiarch building of PLC4X is failing in main branch
To Reproduce
Trigger pipeline building of PLC4X (via merge, tag)
Expected behavior
PLC4X image building should be working
Log Output
https://dev.azure.com/Edgenesis/baed62fa-1aad-4f02-bc6d-bc6cfd242fce/_build/results?buildId=13616&view=logs&jobId=0112d757-5591-5a73-051b-95347f32b3c6
> [linux/arm64 builder 11/11] RUN CGO_ENABLED=1 GOOS=linux GOARCH=arm64 CGO_LDFLAGS="-static" go build -a -v -o /output/deviceshifu cmd/deviceshifu/cmdplc4x/main.go: 10.03 go: error obtaining buildID for go tool compile: fork/exec /usr/local/go/pkg/tool/linux_arm64/compile: invalid argument 10.03 go: error obtaining buildID for go tool compile: fork/exec /usr/local/go/pkg/tool/linux_arm64/compile: invalid argument
Server (please complete the following information):
Additional context
Seems to be a golang/docker issue golang/go#68976
The text was updated successfully, but these errors were encountered:
This only happens using QEMU emulation in pipeline builders, doing manual building for now
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Docker multiarch building of PLC4X is failing in main branch
To Reproduce
Trigger pipeline building of PLC4X (via merge, tag)
Expected behavior
PLC4X image building should be working
Log Output
https://dev.azure.com/Edgenesis/baed62fa-1aad-4f02-bc6d-bc6cfd242fce/_build/results?buildId=13616&view=logs&jobId=0112d757-5591-5a73-051b-95347f32b3c6
Server (please complete the following information):
Additional context
Seems to be a golang/docker issue
golang/go#68976
The text was updated successfully, but these errors were encountered: