【Docker錯誤】starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown - 碼上歡樂

相關內容簡體繁體

【Docker錯誤】starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown

本文轉載自查看原文 2020-09-02 22:55 5839 異常和實戰問題處理方案

一、錯誤信息

[root@VM_0_4_centos ~]# docker exec -it prometheusgrafanalinux_prometheus_1 /bin/bash
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown

二、解決辦法

一般的容器都可以執行/bin/bash，但也有部分容器沒有，那么我們可以用sh來替換/bin/bash

docker exec -it prometheusgrafanalinux_prometheus_1 sh

免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱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 OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"bash\": executable file not found in $PATH": unknown OCI runtime create 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 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 OCI runtime create failed: container_linux.go:380: starting container process caused: exec: 運行docker容器時報錯 exec user process caused "no such file or directory" Docker OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caus #!/bin/bash - no such file or directory 進入Docker 容器 docker exec [CONTAINER ID] bin/bash報錯問題

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