自定義容器啟動腳本報錯：exec user process caused "no such file or directory"

相關內容簡體繁體

自定義容器啟動腳本報錯：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”