docker: Error response from daemon: failed to create task for container: failed to create shim task:

最新推荐文章于 2025-03-05 23:49:51 发布
最新推荐文章于 2025-03-05 23:49:51 发布
阅读量1.2w 收藏 3
点赞数 1
分类专栏： 云服务器 文章标签： docker 容器 运维
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/guo_zhen_qian/article/details/132277608
版权

我的系统是ubuntu22.04，装的docker版本是24.0.5，但是在下载镜像之后去加载时报了这个错误

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: invalid rootfs: not an absolute path, or a symlink: unknown.

ERRO[0000] error waiting for container:

 搜了很多文章，有的说是runc没有安装，我看了一下我的docker，是有runc的

 最后实在没办法了，怀疑可能是docker版本不一致引起的。只能看一下自己想加载的镜像是用哪个版本的docker

docker inspect af25f4ae69d6(镜像ID)

能看到，我想用的这个镜像是用19.03.15版本制作的，

所以就降级docker吧，先删除现有的版本，再安装新版本的，我找不到19.03.15版本的，最后安装了一个20.10.13版本的，确实可以加载了

删除和新安装docker可以参考我的这篇文章

Ubuntu22.04安装docker_guo_zhen_qian的博客-CSDN博客 

@docker error :docker: Error response from daemon: failed to create shim: OCI runtime create failed:
alston_ethannical的博客
11-12 5557
问题描述 docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: error adding seccomp filter rule for syscall clone3: permission denied: unknown.
使用docker报Error response from daemon: Cannot start container container-name: failed to create
javamendou的博客
07-14 1万+
昨天使用Docker进行容器化应用开发的过程中，遇到端口冲突的问题。错误信息：Error response from daemon: Cannot start container container-name: failed to create endpoint endpoint-name on network network-name: Bind for 0.0.0.0:port failed: port is already allocated.
【Bug解决】Error response from daemon: failed to create task for container: failed to create shim task
兴趣使然的创作者
03-05 2051
在执行。
Error response from daemon: failed to create task for container: failed to create shim task: OCI run
weixin_41012767的博客
08-14 6729
1.运行docker version。升级后再查看docker 版本已经有。docker 运行报错 解决办法。版本过低引起的，看一下当前版本。查看docker状态，提示没有。
docker failed to create task for container: failed to create shim task: OCI runtime create failed:
wangjun5159的专栏
06-30 4万+
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v2.task/moby/4a7cc9e9d0d66c8db7f9cd68ffa2631c54d3e3dab4
docker启动失败：failed to create task for container:... not a directory: unknown: Are you trying to mount
A-Itfuture的博客
03-08 4295
docker启动失败： failed to create task for container: ...not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)
（已解决）docker启动容器错误：docker: Error response from daemon: OCI runtime create failed
weixin_67817303的博客
09-23 5322
报错信息的前半部分出现了两个路径“/mydata/elasticsearch/config/elasticsearch.yml”和“/usr/share/elasticsearch/config/elasticsearch.yml”，前一个是我外部主机上的路径，后一个是docker安装的es里面的地址。首先我删除了config目录下的ssdb.conf目录 然后删除了建立失败的ssdb容器 重新run 无报错 出现容器Id。不知道提示这个错误原因有没有其它可能。
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./MediaServer": stat ./MediaServer: no such file or directory: unknown.
最新发布
04-02
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./Media...
Error response from daemon: failed to create task for container:
xdg15294969271的博客
11-22 741
记录一次再麒麟操作系统上遇到的问题。 本来docker好好的能启动，然后服务器重启以后就启动不了docker了。cpu架构是aarch64 Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: container_linux.go:328: starting container process caused "permi
Docker desktop启动容器出错：Error response from daemon
个人学习笔记库，一篇一篇记录成长的足迹
06-09 1万+
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "-it": executable file not found in $PATH: unknown。
Docker 突然挂掉 failed to create shim task: OCI runtime create failed: container_linux.go:345: ...
一个深技大小学生的博客
10-20 1万+
docker OCI runtime create failed问题解决
failed to create task for container: failed to create shim task: OCI runtime create failed: unable
weixin_64517071的博客
11-30 7585
用docker 下载nginx报错记录，及解决办法。 failed to create task for container: failed to create shim task: OCI runtime create failed: unable
【containerd错误解决系列】failed to create shim task, OCI runtime create failed, unable to retrieve OCI...
weixin_42072280的博客
03-28 1万+
【containerd错误解决系列】failed to create shim task, OCI runtime create failed, unable to retrieve OCI runtime error, runc did not terminate successfully
docker容器启动失败（Error response from daemon: error creating overlay mount to /app/docker/overlay2/）
huryer的专栏
07-08 8356
服务器断电，异常关机，重启后，发现无法正常启动docker容器，提示错误： Error response from daemon: error creating overlay mount to /app/docker/overlay2/ 解决办法 根据分析，发现是因为docker服务启动参数中需要开启–selinux-enabled 导致的。尝试修改selinux配置，并重启操作系统，发现docker容器可以正常启动，处理流程如下：.........
记录一个docker启动容器报的错Error response from daemon: OCI runtime create failed: container_linux.go:349
热门推荐
一只大码猴
04-28 4万+
这是启动容器报的错，docker logs没有，容器创建了，但是启动不了容器 Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused “process_linux.go:449: container init caused “ro...
docker 启动容器 报错 Error response from daemon: failed to create shim task: OCI runtime create failed
qiuyuan
03-27 4599
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr
Docker创建容器报错
qq_44106037的博客
07-04 1549
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: container_linux.go:318: starting container process caused “permission denied”: unknown 解决方案：yum remove podman，删除podman，重启docker
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: Running hook #0:: error
03-15
### 解决Docker创建容器时出现OCI运行时错误的问题 当遇到 `docker daemon OCI runtime create failed` 错误时，通常是因为底层的 Linux 容器初始化过程中出现了问题。以下是可能的原因以及解决方案： #### 1. 文件路径配置错误 如果在 Docker 配置文件中指定了不正确的路径或者权限不足，则可能导致此错误。例如，在引用中的命令提到向 `/opt/course/22/security-issues` 添加内容[^1]，这可能会引发权限或其他相关问题。 确保目标目录存在并具有写入权限： ```bash sudo mkdir -p /opt/course/22/ sudo chmod 777 /opt/course/22/ echo "Dockerfile-mysql" >> /opt/course/22/security-issues ``` #### 2. MySQL 启动参数设置不当 MySQL 的认证插件默认可能是 `caching_sha2_password`，而某些客户端可能无法支持该模式。因此可以尝试切换到更兼容的 `mysql_native_password` 认证方式[^2]。 修改 MySQL 配置文件（通常是 `/etc/mysql/my.cnf` 或者 `/etc/my.cnf`），添加如下内容： ```ini [mysqld] default_authentication_plugin=mysql_native_password ``` 重启服务后重新构建镜像： ```bash docker-compose down && docker-compose up --build ``` #### 3. GPU 和 NVIDIA 驱动冲突 如果环境中涉及 CUDA 或 NVIDIA 驱动程序，并且这些组件被删除或损坏，也可能导致 OCI 运行失败。根据引用描述，重装 CUDA 及其依赖项能够解决问题[^3]。 执行以下操作来清理旧版本驱动和工具链： ```bash sudo apt-get purge nvidia* sudo rm -rf /usr/local/cuda* curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add - distribution=$(. /etc/os-release;echo $ID$VERSION_ID) curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list sudo apt-get update sudo apt-get install cuda-11-1 nvidia-container-toolkit sudo systemctl restart docker ``` 完成上述步骤之后再次测试容器启动情况。 --- ### 总结 通过排查文件系统访问控制、调整数据库连接协议以及修复图形处理单元环境等方式可有效缓解此类异常状况的发生概率。具体实施需依据实际场景灵活选用相应措施。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值