


Docker image execution golang executable file: exec /usr/local/go/bin/go: exec format error
php editor Apple may encounter a common error when using Docker: "Docker image executes golang executable file: exec /usr/local/go/bin/go: exec format error". This error is usually caused by the golang executable file in the image not being executed correctly. There are many ways to solve this problem, including checking the permissions of the golang executable file, checking whether the executable file is accessible, checking whether the path to the executable file is correct, etc. By solving this problem, you can ensure that golang executable files are executed correctly in Docker and improve the efficiency and stability of code development.
Question content
I understand that if the go
executable is to be run on another computer, I need to specify its target platform. I'm building a docker image on an Apple machine using the m1 chip:
dockerfile
from --platform=linux/amd64 golang:alpine as build workdir / add go.mod . add go.sum . run go mod download copy . . run cgo_enabled=0 goos=linux goarch=amd64 go build -ldflags="-s -w" -o . from --platform=linux/amd64 scratch workdir /app copy --from=build /foo /foo cmd ["./foo"]
This seems to work since the container is checked after building the output
"architecture": "amd64", "os": "linux"
But when I now use docker-compose
to launch the image on the linux server, I get the error: exec /usr/local/go/bin/go: exec format error
docker-compose.yml
foo: environment: - PORT=${PORT} image: docker.io/name/foo platform: linux/amd64 ports: - "8000:8000" restart: always
I'm pretty new to docker, so I think I'm missing something very obvious here.
Workaround
First, I can confirm that you successfully built the amd64 binary, so this is not a go
issue.
If I run your image (on an amd64 linux system), I don't get the same error you reported. In view of this docker-compose.yaml
:
foo: environment: - port=${port} image: docker.io/chedched/foo platform: linux/amd64 ports: - "8000:8000" restart: always
When running docker-compose up
, I see:
error: for images_foo_1 cannot start service foo: failed to create shim task: oci runtime create failed: runc create failed: unable to start container process: exec: "./foo": stat ./foo: no such file or directory: unknown
This happens because you have set workdir /app
, which makes app
the current working directory in the image, but you have installed the binaries as /foo
. do you need:
Change your
cmd
to reference the correct location:cmd ["/foo"]
Copy after loginor...
Install binaries in
/app
:COPY --from=build /foo ./foo
Copy after loginWith any of these changes, the image will behave as expected.
The above is the detailed content of Docker image execution golang executable file: exec /usr/local/go/bin/go: exec format error. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

This article explains Go's package import mechanisms: named imports (e.g., import "fmt") and blank imports (e.g., import _ "fmt"). Named imports make package contents accessible, while blank imports only execute t

This article details efficient conversion of MySQL query results into Go struct slices. It emphasizes using database/sql's Scan method for optimal performance, avoiding manual parsing. Best practices for struct field mapping using db tags and robus

This article explains Beego's NewFlash() function for inter-page data transfer in web applications. It focuses on using NewFlash() to display temporary messages (success, error, warning) between controllers, leveraging the session mechanism. Limita

This article explores Go's custom type constraints for generics. It details how interfaces define minimum type requirements for generic functions, improving type safety and code reusability. The article also discusses limitations and best practices

This article demonstrates creating mocks and stubs in Go for unit testing. It emphasizes using interfaces, provides examples of mock implementations, and discusses best practices like keeping mocks focused and using assertion libraries. The articl

This article details efficient file writing in Go, comparing os.WriteFile (suitable for small files) with os.OpenFile and buffered writes (optimal for large files). It emphasizes robust error handling, using defer, and checking for specific errors.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

This article explores using tracing tools to analyze Go application execution flow. It discusses manual and automatic instrumentation techniques, comparing tools like Jaeger, Zipkin, and OpenTelemetry, and highlighting effective data visualization
