进入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