自定义容器启动脚本报错：exec user process caused "no such file or directory"

本文转载自查看原文 2017-10-24 00:08 13085 Docker

创建容器起不来，一直是restarting状态，查看容器的报错日志如下：

standard_init_linux.go:178: exec user process caused "no such file or directory"
standard_init_linux.go:178: exec user process caused "no such file or directory"
standard_init_linux.go:178: exec user process caused "no such file or directory"

原因是镜像的entrypoint设置的启动脚本格式是dos，在linux系统上用vi修改成unix格式即可

# vi filename
# :set ff 回车后看到当前文件的fileformat格式
# :set ff=unix 回车后输入:wq保存文件，重新build镜像即可。

免责声明！

本站转载的文章为个人学习借鉴使用，本站对版权不负任何法律责任。如果侵犯了您的隐私权益，请联系本站邮箱yoyou2525@163.com删除。

猜您在找 standard_init_linux.go:207: exec user process caused "no such file or directory" docker运行容器报错standard_init_linux.go:211: exec user process caused “exec format error“的可能解决办法 Dockerfile执行shell脚本报错No such file or directory（又名 Dockerfile中sh脚本格式引发的灾难）【docker报错】starting container process caused "exec: \"-P8080:8080\": executable file not found in $PATH". docker启动容器报错: could not synchronise with container process: not a directory OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown docker制作镜像文件问题standard_init_linux.go:208: exec user process caused "no such file or direct 执行shell脚本报错-bash: ./startup.sh: /bin/sh^M: bad interpreter: No such file or directory shell脚本报错：-bash: xxx: /bin/bash^M: bad interpreter: No such file or directory docker使用非root用户启动容器出现“running exec setns process for init caused \"exit status 40\"": unknown”