当我在windows 10上运行docker映像时。我得到这个错误:
standard_init_linux.go:190: exec user process caused "no such file or directory"
我的docker文件是:
FROM openjdk:8
EXPOSE 8080
VOLUME /tmp
ADD appagent.tar.gz /opt/app-agent
ADD services.jar app.jar
ADD run.sh /run.sh
# Install compiler and perl stuff
RUN apt-get update
RUN apt-get install -y build-essential
RUN apt-get install -y gcc-multilib
RUN apt-get install -y perl
# Install Percona Toolkit
RUN apt-get install --yes percona-toolkit
RUN ["chmod", "+x", "/run.sh"]
ENTRYPOINT ["/run.sh"]
脚本以#!开头/bin/sh
#!/bin/sh
set -e
JAVA_OPTS="-Dfile.encoding=UTF-8 -Djava.security.egd=file:/dev/urandom"
if [ "${APPD_APP_NAME}" != "" ]; then
JAVA_AGENT="-javaagent:/opt/app-agent/javaagent.jar
fi
exec java ${JVM_OPTS} ${JAVA_OPTS} ${JAVA_AGENT} -jar /app.jar
尝试method1:
试着改变#!/bin/sh到#!/bin/bash但是得到同样的错误。
尝试method2:
docker文件中新增dos2unix
RUN apt-get install -y dos2unix
RUN dos2unix /run.sh
存在的问题:
The problem comes from the .sh file. First we must remember that Windows uses \r\n as the end of the line, while Linux and Mac use \n. Git has a feature called autoclrf that is generally set to “true” on Windows. This automatically converts \n to \r\n upon completion of the download from a Git repository, but Git does not make any kind of notice of this, hence the error is generated. This process is good, at least for the other files, but it is not the case for bash files, as is the case for the entrypoint.sh file.
立即解决方案:
打开您最喜欢的代码编辑器并更改导致冲突的文件的行结束符，在我们的示例中是:entrypoint.sh。你可以在软件右下角的Visual Studio Code中做到这一点，单击CRLF，并将文件行的末尾更改为LF。
从下面的链接阅读整篇文章，找到永久的解决方案:
https://davidcasr.medium.com/docker-standard-init-linux-go-211-exec-user-process-caused-no-such-file-or-directory-en-c0cb42edb295
存在的问题:
The problem comes from the .sh file. First we must remember that Windows uses \r\n as the end of the line, while Linux and Mac use \n. Git has a feature called autoclrf that is generally set to “true” on Windows. This automatically converts \n to \r\n upon completion of the download from a Git repository, but Git does not make any kind of notice of this, hence the error is generated. This process is good, at least for the other files, but it is not the case for bash files, as is the case for the entrypoint.sh file.
立即解决方案:
打开您最喜欢的代码编辑器并更改导致冲突的文件的行结束符，在我们的示例中是:entrypoint.sh。你可以在软件右下角的Visual Studio Code中做到这一点，单击CRLF，并将文件行的末尾更改为LF。
从下面的链接阅读整篇文章，找到永久的解决方案:
https://davidcasr.medium.com/docker-standard-init-linux-go-211-exec-user-process-caused-no-such-file-or-directory-en-c0cb42edb295
我解决了一个类似的问题
我的配置:
—> Docker Desktop WSL 2后端—Windows
->需要CGO_ENABLED=1，因为我使用库编译了一个Kafka生产者
confluent-kafka-go.v1 /卡夫卡
我的docker映像已经构建成功，但当我使用docker-compose启动映像时，出现了同样的问题:
xxxxx:~/cp-all-in-one/cp-all-in-one-community# docker-compose up
Recreating ms-c3alert ... done
Attaching to ms-c3alert
ms-c3alert | standard_init_linux.go:211: exec user process caused "no such file or directory"
ms-c3alert exited with code 1
之后，在线程和另一个页面测试所有选项…我发现修复添加在go build句子-ldflags='-w -extldflags "-static"'
RUN CGO_ENABLED=1 GOOS=linux GOARCH=amd64 go build -ldflags='-w -extldflags "-static"' -a -installsuffix cgo -o c3alert .
我正在构建一个Go应用程序，这些答案对我来说都是错误的，所以我想分享我的解决方案。对我来说，我有一个没有Windows参与的Dockerfile(在Mac上编码，尽管在macOS 11和macOS 12上共享一个Dockerfile)。行尾是一样的)。
对我来说，最终的解决方案是，我需要将我的应用程序构建为一个静态链接的二进制文件，它可以在没有外部依赖的情况下运行。我正在为一个Go应用程序构建Dockerfile，它首先在一个Go构建器映像中构建，然后在一个草稿映像中构建。为了允许我的二进制文件从头开始运行，我必须添加CGO_ENABLED=0标志。更多信息请访问reddit页面:https://www.reddit.com/r/golang/comments/pi97sp/comment/hbo0fq6/?utm_source=share&utm_medium=web2x&context=3
我的代码，它最终工作:
############################
# STEP 1 build optimized executable binary
############################
FROM golang:1.16-alpine AS builder
WORKDIR /app
COPY go.mod ./
COPY go.sum ./
RUN go mod download
COPY *.go ./
RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -ldflags="-w -s" -o cl-api
############################
# STEP 2 build a small image
############################
FROM scratch
COPY --from=builder /app/cl-api /
EXPOSE 8000
ENTRYPOINT ["/cl-api"]
