How to Fix Docker's 'standard_init_linux.go:190: exec user process caused \'no such file or directory\'' Error in a Go Web App?

Resolving Docker Error: "standard_init_linux.go:190: exec user process caused "no such file or directory"" with a Go Web App

When running a basic Go web application in Docker, you may encounter an error stating: "standard_init_linux.go:190: exec user process caused "no such file or directory"." This issue arises due to a missing file, script interpreter, or executable library.

In this case, the net import involves libc as a dynamic linked binary. To resolve the issue, you need to specify additional flags during compilation:

CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -a -tags netgo -ldflags '-w' -o mybin *.go

Explanation of the Flags:

• CGO_ENABLED=0: Disables Cgo, which is used for interfacing with C code.
• GOOS=linux: Specifies the target operating system as Linux.
• GOARCH=amd64: Specifies the target architecture as amd64 (64-bit).
• -a: Rebuilds all Go files.
• -tags netgo: Tags the program to use the Go standard library's net package.
• -ldflags '-w': Creates a statically linked executable (removes dependencies on shared libraries).
• -o mybin: Specifies the output binary name as "mybin".

By using these flags, you are creating a statically linked executable that does not depend on external libraries. This should resolve the "no such file or directory" error when running the application in Docker.

The above is the detailed content of How to Fix Docker's 'standard_init_linux.go:190: exec user process caused \'no such file or directory\'' Error in a Go Web App?. For more information, please follow other related articles on the PHP Chinese website!