docker exec提示错误oci runtime error: exec failed: container_linux.go

最新推荐文章于 2026-04-27 09:01:50 发布

原创最新推荐文章于 2026-04-27 09:01:50 发布 · 2.8w 阅读

3 ·

本内容遵循CC 4.0 BY-SA版权协议

收录于

docker 专栏收录该内容

10 篇文章

订阅专栏

本文记录了一次在Docker容器中尝试使用/bin/bash作为shell时遇到的问题及解决方法。当使用sudodockerexec-it命令指定/bin/bash时，遇到了找不到文件或目录的错误。通过替换为/bin/sh或直接使用bash命令成功进入容器。

sudo docker exec -it  569f05d5f4fc /bin/bash

提示错误

rpc error: code = 13 desc = invalid header field value "oci runtime error: 
\ exec failed: container_linux.go:247: 
\ starting container process caused \"exec: \\\"/bin/bash\\\": 
\ stat /bin/bash: no such file or directory\"\n"

尝试

sudo docker exec -it  569f05d5f4fc /bin/sh

sudo docker exec -it  569f05d5f4fc bash

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

木灵木灵

关注关注

7
点赞
踩
3

收藏

觉得还不错? 一键收藏
3
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

专栏目录

Docker 问题集锦(24) - 解决：OCI runtime exec failed: exec failed: container_linux.go:367

liuzhen007的专栏

01-30

2223

问题今天使用命令进入容器的时候，遇到了如下报错信息： OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

3 条评论您还未登录，请先登录后发表或查看评论

docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting cont

lyc0424的博客

12-12

2万+

docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \"sh\": executable file not found in $PATH": unknown. 环境：Ubuntu16.04 虚...

Docker报错：OCI runtime exec failed exec failed container_linux.go380 starting container process详解

m0_67402564的博客

06-02

3513

老规矩：先上答案把脚本类型 /bin/bash，尝试换为 /bin/sh 试一下，如果你想对两种shell的区别有深入了解，点击这里。注意：如果你在Dockerfile中引用了自定义脚本，比如：entrypoint: ./entrypoint.sh，如果没有单独给该脚本通过chmod +x ./entrypoint.sh 添加执行权限，也可能会报这个错误。本机脚本解释器类型有4种。最常见的是前两种(usr)/bin/sh和(usr)/bin/bash，还有一些不是很常见的脚本类型：ash、ksh、csh

OCI runtime exec failed: exec failed: container_linux.go:370 docker exec -it 失败的解决方法

LoneShadovv的专栏

03-23

4321

运行了个docker，想进shell看看，使用常规的命令docker exec -it<container ID> /bin/bash 发现报错： ♥root-22:33:34=>>~# docker exec -it 2ade3c165388 /bin/bash OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/b...

别再只会用/bin/bash了！Docker容器报错‘OCI runtime exec failed’的三种排查思路与终极解决方案

最新发布

weixin_42525369的博客

04-27

272

本文深入解析Docker容器报错‘OCI runtime exec failed’的根源与解决方案，特别针对现代精简镜像（如Alpine、Distroless）中/bin/bash缺失问题。提供三种实用排查方法：镜像类型确认、替代Shell尝试和nsenter命名空间进入，并分享生产环境最佳实践，帮助开发者高效解决容器调试难题。

使用docker exec 进入容器报错“OCI runtime exec failed”

ixuery的博客

03-06

3840

报错信息： OCI runtime exec failed: exec failed: container_linux.go:296: starting container process caused "process_linux.go:78: starting setns process caused \"fork/exec /proc/self/exe: no such file or directory\"": unknown 可能原因：可能是docker 守护进程出了问题，尝试重启dock

Docker使用时遇到的问题汇总

sinat_34241861的博客

12-22

1701

1、执行docker exec -it test3 /bin/bash命令报错如下 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 exec -it test3 /bin/sh // 方

【docker】pc error: code = 13 desc = invalid header field value "oci runtime error: exec failed 解决方法

LaoLi0519的博客

09-20

1079

docker 报错，无法进入容器 rpc error: code = 13 desc = invalid header field value “oci runtime error: exec failed: container_linux.go:247: starting container process caused “process_linux.go:75: starting setns...

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

weixin_42726887的博客

12-11

1万+

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

解决Error response from daemon: oci runtime error: container_linux.go:235: starting container process

weixin_45627271的博客

04-19

2573

解决Error response from daemon: oci runtime error: container_linux.go:235: starting container process

docker 或 docker-compose 安装成功报错 OCI runtime create failed: container_linux.go:345

夜~狠冷

02-08

1万+

docker 或 docker-compose 安装成功报错 OCI runtime create failed: container_linux.go:345 Creating mysql … error ERROR: for mysql Cannot start service mysql: OCI runtime create failed: container_linux.go:345:...

oci runtime error: exec failed: container_linux.go:247: starting container process caused “exec: \“/

runzhliu大数据/容器日记

07-07

5170

在运行 mpi-operator 之后，想进去容器查看一下，于是执行下面的命令报错。 [root@TENCENT64site /data/runzhliu/mpi]# kubectl exec -it -n kube-system mpi-operator-bbf56967f-ht8bx /bin/sh rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container p

记一次docker启动失败的问题排查

feixd0419的博客

03-02

1639

Error response from daemon: oci runtime error: container_linux.go:290: starting container process caused "process_linux.go:369: container init caused \"write /proc/sys/kernel/shmmni: invalid argument\

OCI runtime exec failed: exec failed: container_linux.go:349: starting container 解决方法

weixin_46941625的博客

08-06

1万+

docker执行命令:docker exec -it redis1 /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 报错场景:我是pull了一个registry镜像，准备搭建私有库。运行了

已解决 docker: Error response from daemon: OCI runtime create failed: container_linux.go:349

GoCloudNative - 云原生技术的探索者。

09-19

2万+

嗨，各位猫头虎博主的小伙伴们！。本文将详细分析该问题的根本原因、解决方法以及如何避免类似的状况。让我们一起来解决这个Bug吧！在云原生应用开发中，Docker是不可或缺的工具，但在使用过程中会遇到各种问题，OCI runtime create失败就是其中之一。本文通过深入分析问题的原因，提供了解决方法和避免类似问题的建议。希望本文能帮助您更好地理解和应对这个常见的Bug。

使用Docker 报错OCI runtime exec failed: exec failed: unable to start container process: exec: “xxx“: exe

javamendou的博客

06-21

2万+

前些天在使用 Docker 运行一个容器时，遇到了一个报错：OCI runtime exec failed: exec failed: unable to start container process: exec: “xxx“: exec

解决进入Docker容器报错-OCI runtime exec failed: exec failed: unable to start container process