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

最新推荐文章于 2024-07-26 11:45:00 发布

九师兄

最新推荐文章于 2024-07-26 11:45:00 发布

阅读量6.9k

点赞数 3

分类专栏：工具-docker

本文为博主九师兄（QQ:541711153 欢迎来探讨技术）原创文章，未经允许博主不允许转载。

本文链接：https://blog.csdn.net/qq_21383435/article/details/106134163

版权

工具-docker 专栏收录该内容

49 篇文章 448 订阅 ¥9.90 ¥99.00

订阅专栏

本文介绍了在Mac环境下遇到的Docker OCI runtime exec failed错误，详细解析了问题背景及提供了解决此类错误的具体方法。

摘要由CSDN通过智能技术生成

在这里插入图片描述

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": unknown

mac下进入容器产生的错误

2.解决办法

了解本专栏

订阅专栏解锁全文

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

九师兄

关注关注

3
点赞
踩
4

收藏

觉得还不错? 一键收藏
打赏
0
评论
复制链接

分享到 QQ

分享到新浪微博

扫一扫

专栏目录

订阅专栏

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

liu_chen_yang的博客

02-20

3779

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: container_linux.go:348

梦影剑魂的博客

01-30

8474

使用git bash 工具进入到kafka时报错 OCI runtime exec failed: exec failed: container_linux.go:348，原命令如下： winpty docker exec -it kafka-0 /bin/bash 一直进不到容器中，可以尝试以下命令： winpty docker exec -it kafka-0 bash ...

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

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

最新发布

小哎呀的博客

07-26

378

问题解决方法：解决进入Docker容器报错-OCI runtime exec failed: exec failed: unable to start container process-CSDN博客

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

m0_67402564的博客

06-02

2906

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

使用docker exec进入容器报错：OCI runtime exec failed: exec failed: container_linux.go:348: starting container

aovenus的专栏-测试新时代（微信公众号：测试新时代）

01-20

3125

【问题】使用docker exec -it a2d69c075875 /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": unknown 【解决方法】使用docker exec -it a2d69

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

Sherry

11-25

1万+

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

docker部署，启动失败 OCI runtime create failed: container_linux.go:348:

samoyan的博客,记录技术成长~

08-30

3631

docker run hello-world 出现一下问题， docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:297:copying bootstrap data to pipe caused \"write init-p: broken pipe\"": unknown.

docker进入容器报错：OCI runtime exec failed: exec failed: container_linux.go:345: starting container proces

北国有鱼的博客

05-03

1万+

docker进入容器报错： OCI runtime exec failed: exec failed: container_linux.go:345: starting container process caused “exec: “F:/Workspace/Git/usr/bin/sh”: stat F:/Workspa ce/Git/usr/bin/sh: no such file or d...

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 虚...

OCI runtime create failed: container_linux.go:348: starting container process caused \“exec: \\\“pyt

重剑无锋博客

01-28

1235

应该是docker镜像没有安装python

docker&&ubuntu:14.04&&OCI runtime create failed: container_linux.go:348: starting container process

dfq737211338的博客

10-16

5470

docker&&ubuntu:14.04&&OCI runtime create failed: container_linux.go:348: starting container process caused错误示例：问题分析：解决方法：方法一：升级当前操作系统方法二：更改当前docker版本错误示例： root@tcpserver01HZ:~# docker...

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

飞乐鸟的博客

07-26

260

docker进入容器： docker exec -it fda986ac8985 /bin/bash 解决办法: docker exec -it fda986ac8985 /bin/sh 或者 docker exec -it fda986ac8985 bash 或者 docker exec -it fda986ac8985 sh

Docker OCI runtime exec failed: exec failed: container_linux.go:349

u011017284的博客

03-19

8511

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 OCI runtime exec failed: exec fa...

centos7 docker 启动镜像报错：OCI runtime create failed:container_linux.go:348: starting container process

LXIT_pineapple的博客

04-25

2564

centos7 docker 启动镜像报错：OCI runtime create failed:container_linux.go:348: starting container process caused "process_linux [root@localhost log]# docker run -ithello-world /bin/dash 解决方案：更换合适的docker版本： 1.暂停docker ： stop docker sudo systemctl stop docker

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

weixin_42962634的博客

06-16

4557

错误内容： docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown. 查了半天的博客，最后终于找到了解决的办法，不一定适用于其他

docker重启容器，报错：OCI runtime create failed: container_linux.go:348: starting container process caused “

04-24

3819

docker重启容器，报错：OCI runtime create failed: container_linux.go:348: starting container process caused " 执行：echo 1 > /proc/sys/vm/drop_caches 然后继续重启

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报错之：OCI runtime exec failed: exec failed: container_linux.go:367: starting container process c

11-24

Docker报错之：OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: "binbash": executable file not found in $PATH: unknown，这个错误通常是由于容器中缺少/bin/bash文件导致的。可以通过以下步骤解决该问题： 1. 确认容器中是否存在/bin/bash文件，可以通过以下命令进入容器内部查看： ```shell docker exec -it <container_id> /bin/bash ``` 如果提示/bin/bash文件不存在，则需要安装bash。 2. 在Dockerfile文件中添加安装bash的命令，例如： ```dockerfile RUN apt-get update && apt-get install -y bash ``` 这将在构建镜像时安装bash。 3. 如果容器中已经安装了bash，但仍然出现该错误，则可能是由于PATH环境变量未正确设置。可以通过以下命令在容器内部设置PATH环境变量： ```shell export PATH=$PATH:/bin:/usr/bin:/usr/local/bin ``` 这将将/bin、/usr/bin和/usr/local/bin添加到PATH环境变量中。