進入Docker 容器 docker exec [CONTAINER ID] bin/bash報錯問題 - 碼上快樂

相關內容簡體繁體

進入Docker 容器 docker exec [CONTAINER ID] bin/bash報錯問題

本文轉載自查看原文 2020-03-31 16:26 7236 docker

我們直接使用命令 docker exec -it ceff85e1747d /bin/bash 在有些情況下會報出

OCI runtime exec failed: exec failed: container_linux.go:337: starting container process caused

"exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown

這個錯誤說明鏡像不包含適合bash的風格操作，沒有這樣的文件或目錄

可能你的鏡像基於busybox，它沒有bash shell。但他在/bin/sh有一個shell

直接執行 docker exec -ti ceff85e1747d /bin/sh 就可以進入容器里面l

免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。

猜您在找 docker - 進入容器報錯：OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown docker 部署mysql tomcat時在root@localhost~下——-——docker exec -it 容器名 /bin/bash 報錯【Docker錯誤】starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown docker exec進入容器的原理 HyperLedger Fabric 運行docker exec -it cli bash的時候 Error: No such container: cli docker exec 無法進入容器 OCI runtime exec failed、container_linux.go:348: starting container process caused "process_linux.go:78: starting setns process caused \"fork/exec /proc/self/exe: no such file 進入正在運行的 docker 容器（docker container） docker OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"bash\": executable file not found in $PATH": unknown 查看容器ip時報錯“OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "ip": executable file not found in $PATH: unknown” 關於啟動Docker容器的錯誤：OCI runtime create failed: container with id exists

粵ICP備18138465號 © 2018-2025 CODEPRJ.COM