OCI runtime exec failed: exec failed:解决方法

最新推荐文章于 2024-08-09 14:18:21 发布

遗失的曾经！

最新推荐文章于 2024-08-09 14:18:21 发布

阅读量5.7w

点赞数 35

分类专栏：其他

本文链接：https://blog.csdn.net/u014609263/article/details/90175394

版权

其他专栏收录该内容

3 篇文章

订阅专栏

本文解决在Docker中使用Alpine镜像时，尝试通过docker exec命令以/bin/bash进入容器却失败的问题。通常，Alpine镜像默认Shell为/bin/sh，而非/bin/bash。文章指导如何正确使用docker exec命令，指定/bin/sh来成功进入Alpine容器。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

引入了一个镜像，由于要修改一个参数，因此要进入容器中，一般使用

docker exec -it 容器名 /bin/bash

然而报错

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

原来该镜像是使用alpine制作的，要进入该容器需要输入

docker exec -it 容器名 /bin/sh

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

遗失的曾经！

关注关注

35
点赞
踩
19

收藏

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

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

专栏目录

OCI runtime exec failed: exec failed: unable to start container process: exec: “mongo“: executablexx

猿小白的博客

09-01

209

使用docker部署mongo的时候，遇到这个报错信息。

群晖、飞牛NAS容器进入终端失败？一步步教你解决Docker Bash错误！（OCI runtime exec failed: exec failed）

最新发布

XiaoqiangClub的博客

11-23

1415

群晖、飞牛NAS容器进入终端失败？一步步教你解决Docker Bash错误！（OCI runtime exec failed: exec failed）

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

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

m0_67402564的博客

06-02

3219

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

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

Sherry

11-25

2万+

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

Docker 报错：OCI runtime exec failed: exec failed: unable to start container process: exec: “xxx“: exec

Htupc的博客

01-23

8576

Docker 报错：OCI runtime exec failed: exec failed: unable to start container process: exec: "xxx": executable file not found in $PATH: unknown

OCI runtime exec failed:exec failed:解决办法

sinat_26308147的博客

11-24

703

进入容器 docker run -it 容器ID /bin/bash,报错OCI runtime exec failed:exec failed:container_linux.go:380:starting container process caused ...解决办法：用相对路径 docker run -it 容器ID ./bin/bash。

使用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: write /tmp/runc-process35...: no space left on device:unknown】

weixin_45072910的博客

08-31

2152

进入docker报错：OCI runtime exec failed: write /tmp/runc-process358148171: no space left on device: unknown 解决记录

【Docker】OCI runtime exec failed: exec failed: container_linux.go:348: starting container process cau

九师兄

07-01

7159

1.背景 docker执行命令 (base) lcc@lcc flink-1.10.0$ docker exec -it mysqld-exporter /bin/bash OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknow.

【Docker】常见容器问题解决#OCI runtime create failed: container_linux.go:349: starting container process

liu_chen_yang的博客

02-20

4575

ERROR: for nginx Cannot start service nginx: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/data/docker-compose/n

OCI runtime exec failed: exec failed: unable to start container process: exec: “ip“: execu

sxlishaobin的博客

02-04

5411

docker exex -it [容器id] bash。原因：因为docker 容器是精简版的缺少一些命令。docker 容器输入ip adrr 报错。4 安装完以后退出exit。3 安装iproute2。5 再次执行命令不报错。

【已解决】OCI runtime exec failed: open /dev/pts/1: operation not permitted: unknown

blackome的博客

08-09

606

原因是因为可能某一次daemon-reload后，由1.1.3 runc的bug引发了exec失败，解决办法是升级runc。7、检查runc是否升级成功 sudo docker info| grep runc。2、上传到服务器，修改名字并赋予权限。OK，现在能正常exec进入容器了。3、备份原有的runc。5、替换新版本runc。4、停止docker。6、启动docker。

OCI runtime exec failed: exec failed:

weixin_41195786的博客

12-28

1万+

遇到这种问题的，想必是在使用docker镜像进入容器了。在做docker exec -it 容器名 /bin/bash的时候，它会提示你OCI runtime exec failed: exec failed:这个错。我遇到的情况是这样的，当我启动容器想要进到容器里面的时候，它就给我提示这个错误，查了一下资料，原因多半都是因为你引入的镜像是alpine的镜像。比方说我引入的是alpine-open...

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

ixuery的博客

03-06

3597

报错信息： 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进入容器报错OCI runtime exec failed: exec failed: unable to start container process: chdir to cwd (“

qq_39691492的博客

05-24

2591

解决进入docker容器报错OCI runtime exec failed: exec failed: unable to start container process: chdir to cwd ("/Xxx") set in config.json failed: no such file or directory: unknown

Docker OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caus

热门推荐

程序员

04-06

6万+

docker执行命令:docker exec -it 1e33b26152e1 /bin/bash 在进入容器报错:OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no su...

docker进入容器报错：OCI runtime exec failed: exec failed

logic_c的博客

08-14

8542

使用 sudodocker exec -it 容器名 /bin/bash 进入容器时报错。错误信息： OCI runtime exec failed: exec failed: container_linux.go:345: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such fil...

OCI runtime exec failed: exec failed: unable to start container process:

08-30

OCI runtime exec failed: exec failed: unable to start container process: exec: "xxx": exec 是 Docker 运行容器时的一个报错信息，它表示在执行命令时无法启动容器进程。具体的错误原因可能有多种情况。其中一个可能的原因是容器中缺少要执行的命令所需的可执行文件，它可能没有在容器内的 $PATH 环境变量中。这可以通过在容器中安装相应的软件包来解决。另一个可能的原因是容器运行时环境的配置问题。这可以通过确认容器是否正常启动，以及检查容器的配置和依赖项来解决。根据引用和引用中的解决办法，您可以尝试安装所需的命令或确认容器的网络配置是否正确。123 #### 引用[.reference_title] - *1* [使用Docker 报错OCI runtime exec failed: exec failed: unable to start container process: exec: “xxx...](https://blog.csdn.net/javamendou/article/details/131327328)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] - *2* *3* [Docker 报错：OCI runtime exec failed: exec failed: unable to start container process: exec: “xxx“:...](https://blog.csdn.net/Htupc/article/details/128753275)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]