Error response from daemon ... no space left on device docker启动容器服务报错

docker 启动容器服务的时候,报错no space left on device

1. 检查磁盘是否用光

3.检查inode是否耗光,从截图看到是inode耗光导致出现问题:

进入到/run里面看看是哪些文件耗光了:#for i in ./*; do echo $i; find $i | wc -l; done
查看到最大的是/run/docker/libcontainerd/下面一部分容器耗光的。
该目录的结构是:
/run/docker/libcontainerd/2b9251bcc7a4484662c8b69174d92b3183f0f09a59264b412f14341ebb759626
├── config.json # 容器配置
├── init-stderr # 标准错误输出
├── init-stdin # 标准输入
└── init-stdout # 标准输出.
主要耗光inode的是标准输入输出和错误输出:

进入容器,查看:

重启容器,会释放:

后续查到该容器服务产生的日志也非常大,有50多G。

建议:对容器的日志进行切割。

原文地址:https://www.cnblogs.com/zoujiaojiao/p/10886363.html

时间: 2024-08-08 00:50:33

Error response from daemon ... no space left on device docker启动容器服务报错的相关文章

docker pull / docker login 报错 Error response from daemon: Get https://registry-1.docker.io/v2/: x509

docker pull 和 docker login 的时候报错 Error response from daemon: Get https://registry-1.docker.io/v2/: x509: certificate is valid for bw-production.space, brickworksoftware.com, *.bw-production.space, *.brickworksoftware.com, not registry-1.docker.io 从报错

docker端口映射或启动容器时报错Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen

现象: [[email protected] ~]# docker run -d -p 9000:80 centos:httpd /bin/sh -c /usr/local/bin/start.shd5b2bd5a7bc4895a973fe61efd051847047d26385f65c278aaa09e4fa31c4d76docker: Error response from daemon: driver failed programming external connectivity on

docker export import后,导入镜像,启动时的错误,Error response from daemon: No command specified

Docker的流行与它对容器的易分享和易移植密不可分,用户不仅可以把容器提交到公共服务器上,还可以把容器导出到本地文件系统中.同样,我们也可以把导出的容器重新导入到Docker运行环境中.Docker的容器导入导出分别用import和export命令完成. 1.导出容器export 注意:export导出的是容器,不是镜像. [plain] view plain copy docker export <CONTAINER ID > > my_container.tar docker ex

Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2

环境:centos7.1 docker run -t -i centos /bin/bash 运行上面的命令开启容器时报错: /usr/bin/docker-current: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/8c4e909f7bd85dd94ac3483b209643dd02b4e45adfc0b8ee141a95214903a5c8/merged: inva

docker: Error response from daemon: driver failed programming external connectivity on endpoint jolly_shockley

1. docker 启动image错误 docker: Error response from daemon: driver failed programming external connectivity on endpoint jolly_shockley (957a1271cd0ae4f9f28163b7cdf5c17d6110fcd6ccd2ca79f2cf0ab8c67dfd52): (iptables failed: iptables --wait -t nat -A DOCKER

docker启动时报错Error response from daemon: driver failed programming external connectivity on endpoint *

公司服务器由于断电重启,部署在docker服务上的一些web服务需要重新开启容器, [root@localhost ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d77c2c6b3650 chandao:latest "/app/docker-entrypo…" 7 days ago Up About an hour 0.0.0.0:7075->80/tcp chandao 当重新开启容器的

Error response from daemon: conflict: unable to remove repository reference 解决方案

由于前一章演示用的镜像没什么用准备删除 docker image rm hello-world:latest Error response from daemon: conflict: unable to remove repository reference "hello-world:latest" (must force) - container 32a5e6dd8f62 is using its referenced image fce289e99eb9 来自守护进程的错误响应:

docker: Error response from daemon: OCI runtime create failed 解决办法

错误原因 在新服务器上安装好docker后,发现无法运行,经常一顿搜索后,发现是docker安装的版本过高,最新版本docker-18.06 的核心好像没有经过充分的测试就发布了. 导致一运行,就提示: docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:301: runn

运行容器出现docker: Error response from daemon: driver failed programming external connectivity on endpoint elegant_ptolemy (7fe85ca6bd744449ff82b81c1577d73b6821c4e51780c8238fad6aa0cb940522): (iptables fai

运行容器时出现以下报错: docker: Error response from daemon: driver failed programming external connectivity on endpoint elegant_ptolemy (7fe85ca6bd744449ff82b81c1577d73b6821c4e51780c8238fad6aa0cb940522):  (iptables failed: iptables --wait -t nat -A DOCKER -p tc