Why Does My Dockerized Go Web App Fail with 'No Such File or Directory'?

Docker Image Exec Error: "No Such File or Directory" When Running Go Web App

A recently created Docker image is encountering an error when running, displaying the message "standard_init_linux.go:190: exec user process caused "no such file or directory"." This error prevents the Go web application from executing properly within the Docker container.

The root cause of this error lies in a missing file, a script missing its interpreter, or an executable lacking a required library. In this instance, the import of the "net" package in the Go code results in the automatic inclusion of libc as a dynamically linked binary. To verify this, utilize the "ldd" command on the binary.

To resolve this issue, additional build flags must be provided:

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

These flags disable CGO (the Go compiler's built-in support for C), specify the target operating system and architecture, and produce a statically linked binary. This ensures that all necessary libraries are embedded within the executable, eliminating the need for external dependencies.

By incorporating these flags during the Go build process, the resulting Docker image will include the required dependencies and the error message will be resolved, allowing the Go web application to execute successfully within the Docker container.

The above is the detailed content of Why Does My Dockerized Go Web App Fail with 'No Such File or Directory'?. For more information, please follow other related articles on the PHP Chinese website!