Home > Backend Development > Golang > Docker image execution golang executable file: exec /usr/local/go/bin/go: exec format error

Docker image execution golang executable file: exec /usr/local/go/bin/go: exec format error

PHPz
Release: 2024-02-09 10:18:29
forward
771 people have browsed it

Docker 镜像执行 golang 可执行文件:exec /usr/local/go/bin/go: exec 格式错误

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"]
Copy after login

This seems to work since the container is checked after building the output

"architecture": "amd64",
"os": "linux"
Copy after login

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
Copy after login

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
Copy after login

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
Copy after login

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 login

    or...

  • Install binaries in /app:

    COPY --from=build /foo ./foo
    Copy after login

    With 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!

source:stackoverflow.com
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template