docker启动报错Job for docker.service failed because a configured resource limit was exceeded

最新推荐文章于 2024-08-27 08:24:33 发布
原创 最新推荐文章于 2024-08-27 08:24:33 发布 · 4k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文详细介绍了当Docker启动时报错“Jobfordocker.servicefailedbecauseaconfiguredresourcelimitwasexceeded”时的解决方案。包括结束Docker进程、清除所有已订的规则、关闭并删除网桥docker0，最后重启Docker服务的具体步骤。

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

docker 启动报错：Job for docker.service failed because a configured resource limit was exceeded. See “systemctl status docker.service” and “journalctl -xe” for details.
启动docker报错
查看docker状态
解决办法：
pkill docker #结束docker 进程
iptables -t nat -F #清除所有的已订的规则
ifconfig docker0 down #关掉docker0网络
brctl delbr docker0 #删除网桥docker0
service docker restart #启动docker服务

*欢儿*
关注
nginx 网站突然访问不了的问题排查记录（Job for nginx.service failed because a configured resource limit was exceeded）
一碗清深的博客
06-13 465
某一天，在浏览器开打网站，一直处于加载的状态，等待了许久都未进入页面，于是登陆服务器查看后端进程都正常，检查了证书也是正常的。
Docker安装Redis 指定外部文件redis.conf启动
qq_29138685的博客
08-01 710
0、linux系统为阿里云的centos7.4 1、拉取Redis镜像: docker pull redis:4.0.14 2.创建文件/home/redis/conf/redis.conf，用于挂载Redis配置文件(文章结尾附上配置文件)： mkdir -p /home/redis/conf/ ##创建文件夹 touch /home/redis/conf/redis.conf ## ...
Docker启动报错“Job for docker.service failed because a configured resource limit was exceeded.
qq_51756376的博客
02-24 3168
Docker启动报错"Job for docker.service failed because a configured resource limit was exceeded. See “systemctl status docker.service” and “journalctl -xe” for details." 配置docker跨主机集群之flannel之后第二天启动docker报错"Job for docker.service failed because a configured reso
安装部署Nginx启动Nginx时报错:Job for nginx.service failed because a configured resource limit was exceeded.
llgl56789的博客
08-27 669
在CentOS中安装部署Nginx，输入systemctl start nginx启动Nginx时报如下错误：Job for nginx.service failed because a configured resource limit was exceeded. See "systemctl status nginx.service" and "journalctl -xe" for details.途中给了解决办法，让查看nginx的运行状态和日志那就按照它给的来查看日志：journalctl -xe
报错：Job for zabbix-server.service failed because a configured resource limit was exceede.....
qq_43059674的博客
09-27 1万+
报错： Job for zabbix-server.service failed because a configured resource limit was exceeded. See "systemctl status zabbix-server.service" and "journalctl -xe" for details. 关闭SeLinux 即可： 临时关闭：setenforce...
问题：Job for zabbix-agent.service failed because a configured resource limit was exceeded.See “syst...
weixin_40268588的博客
08-26 5664
如启动或者重启Zabbix-Agent出现以下提示： 这时需要关闭Selinux vi /etc/selinux/config 将 SELINUX=enforcing改为disabled，再setenforce 0
docker实际生产中遇到的问题及解决办法
weixin_38924998的博客
02-05 2121
解决：这里有containerd的目录，需要将/var/lib/docker整个目录删除掉。解决：删除目录 /run/containerd/containerd.sock。
Docker 安装 redis,并配置持久化,redis默认的redis.conf文件
qq_52252193的博客
04-26 4926
1. docker pull redis:6.0.8 2.命令提醒：容器卷记得加入--privileged=true 3.本机建立文件夹，用来映射容器卷 建立 /mytest-docker/redis 建立 redis.conf文件 修改里面的内容 （随便拷贝一个已经安装过的redis.conf 如果没有，下面我贴附了 redis 出厂默认的 conf 文件 允许redis外地连接 必须 注释掉 # bind 127.0.0.1 修改 daem...
7月 08 02:08:48 sw-VMware-Virtual-Platform systemd[1]: docker.service: Deactivated successfully. 7月 08 02:08:48 sw-VMware-Virtual-Platform systemd[1]: Stopped docker.service - Docker Application Container Engine. 7月 08 02:08:48 sw-VMware-Virtual-Platform systemd[1]: Starting docker.service - Docker Application Container Engine... 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.175835934+08:00" level=info msg="Starting up" 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.176582933+08:00" level=info msg="OTEL tracing is not configured, using no-op tracer provider" 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.176673256+08:00" level=info msg="CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory" dir=/var/run/cdi 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.176709209+08:00" level=info msg="CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory" dir=/etc/cdi 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.176779556+08:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf" 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.183689488+08:00" level=info msg="Creating a containerd client" address=/run/containerd/containerd.sock timeout=1m0s 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.198376903+08:00" level=info msg="[graphdriver] using prior storage driver: overlay2" 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.198568602+08:00" level=info msg="Loading containers: start." 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.783213421+08:00" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint_count 46cdc042d3e3e9685261ee9652e8672806c462c4d7a00ed357e59845b2e9059d], retrying...." 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.807172158+08:00" level=info msg="Loading containers: done." 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.815720498+08:00" level=info msg="Docker daemon" commit=5beb93d containerd-snapshotter=false storage-driver=overlay2 version=28.3.1 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.815768545+08:00" level=info msg="Initializing buildkit" 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.827495405+08:00" level=info msg="Completed buildkit initialization" 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.831627620+08:00" level=info msg="Daemon has completed initialization" 7月 08 02:08:48 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:08:48.831703735+08:00" level=info msg="API listen on /run/docker.sock" 7月 08 02:08:48 sw-VMware-Virtual-Platform systemd[1]: Started docker.service - Docker Application Container Engine. 7月 08 02:09:17 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:17.991463062+08:00" level=warning msg="Error getting v2 registry: Get \"https://registry.docker-cn.com/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 7月 08 02:09:17 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:17.991507785+08:00" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry.docker-cn.com/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 7月 08 02:09:18 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:18.038325673+08:00" level=warning msg="Error getting v2 registry: Get \"https://docker.mirrors.ustc.edu.cn/v2/\": dial tcp: lookup docker.mirrors.ustc.edu.cn on 127.0.0.53:53: no such host" 7月 08 02:09:18 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:18.038354114+08:00" level=info msg="Attempting next endpoint for pull after error: Get \"https://docker.mirrors.ustc.edu.cn/v2/\": dial tcp: lookup docker.mirrors.ustc.edu.cn on 127.0.0.53:53: no such host" 7月 08 02:09:18 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:18.074104206+08:00" level=warning msg="Error getting v2 registry: Get \"https://hub-mirror.c.163.com/v2/\": dial tcp: lookup hub-mirror.c.163.com on 127.0.0.53:53: no such host" 7月 08 02:09:18 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:18.074122866+08:00" level=info msg="Attempting next endpoint for pull after error: Get \"https://hub-mirror.c.163.com/v2/\": dial tcp: lookup hub-mirror.c.163.com on 127.0.0.53:53: no such host" 7月 08 02:09:33 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:33.075713810+08:00" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 7月 08 02:09:33 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:33.075758059+08:00" level=info msg="Not continuing with pull after error" error="Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 7月 08 02:09:33 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:09:33.076391178+08:00" level=error msg="Handler for POST /v1.51/images/create returned error: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 7月 08 02:10:22 sw-VMware-Virtual-Platform systemd[1]: Stopping docker.service - Docker Application Container Engine... 7月 08 02:10:22 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:10:22.598062038+08:00" level=info msg="Processing signal 'terminated'" 7月 08 02:10:22 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:10:22.598683148+08:00" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby 7月 08 02:10:22 sw-VMware-Virtual-Platform dockerd[4104]: time="2025-07-08T02:10:22.598888369+08:00" level=info msg="Daemon shutdown complete" 7月 08 02:10:22 sw-VMware-Virtual-Platform systemd[1]: docker.service: Deactivated successfully. 7月 08 02:10:22 sw-VMware-Virtual-Platform systemd[1]: Stopped docker.service - Docker Application Container Engine. 7月 08 02:10:22 sw-VMware-Virtual-Platform systemd[1]: Starting docker.service - Docker Application Container Engine... 7月 08 02:10:22 sw-VMware-Virtual-Platform dockerd[4499]: unable to configure the Docker daemon with file /etc/docker/daemon.json: invalid character 'j' looking for beginning of value 7月 08 02:10:22 sw-VMware-Virtual-Platform systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE 7月 08 02:10:22 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:10:22 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine. 7月 08 02:10:24 sw-VMware-Virtual-Platform systemd[1]: docker.service: Scheduled restart job, restart counter is at 1. 7月 08 02:10:24 sw-VMware-Virtual-Platform systemd[1]: Starting docker.service - Docker Application Container Engine... 7月 08 02:10:24 sw-VMware-Virtual-Platform dockerd[4510]: unable to configure the Docker daemon with file /etc/docker/daemon.json: invalid character 'j' looking for beginning of value 7月 08 02:10:24 sw-VMware-Virtual-Platform systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE 7月 08 02:10:24 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:10:24 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine. 7月 08 02:10:27 sw-VMware-Virtual-Platform systemd[1]: docker.service: Scheduled restart job, restart counter is at 2. 7月 08 02:10:27 sw-VMware-Virtual-Platform systemd[1]: Starting docker.service - Docker Application Container Engine... 7月 08 02:10:27 sw-VMware-Virtual-Platform dockerd[4520]: unable to configure the Docker daemon with file /etc/docker/daemon.json: invalid character 'j' looking for beginning of value 7月 08 02:10:27 sw-VMware-Virtual-Platform systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE 7月 08 02:10:27 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:10:27 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine. 7月 08 02:10:29 sw-VMware-Virtual-Platform systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. 7月 08 02:10:29 sw-VMware-Virtual-Platform systemd[1]: docker.service: Start request repeated too quickly. 7月 08 02:10:29 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:10:29 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine. 7月 08 02:11:05 sw-VMware-Virtual-Platform systemd[1]: docker.service: Start request repeated too quickly. 7月 08 02:11:05 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:11:05 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine. 7月 08 02:24:59 sw-VMware-Virtual-Platform systemd[1]: Starting docker.service - Docker Application Container Engine... 7月 08 02:24:59 sw-VMware-Virtual-Platform dockerd[9896]: time="2025-07-08T02:24:59.073177400+08:00" level=info msg="Starting up" 7月 08 02:24:59 sw-VMware-Virtual-Platform dockerd[9896]: time="2025-07-08T02:24:59.073829778+08:00" level=info msg="OTEL tracing is not configured, using no-op tracer provider" 7月 08 02:24:59 sw-VMware-Virtual-Platform dockerd[9896]: time="2025-07-08T02:24:59.073896097+08:00" level=info msg="CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory" dir=/etc/cdi 7月 08 02:24:59 sw-VMware-Virtual-Platform dockerd[9896]: time="2025-07-08T02:24:59.073903656+08:00" level=info msg="CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory" dir=/var/run/cdi 7月 08 02:24:59 sw-VMware-Virtual-Platform dockerd[9896]: time="2025-07-08T02:24:59.073974271+08:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf" 7月 08 02:24:59 sw-VMware-Virtual-Platform dockerd[9896]: time="2025-07-08T02:24:59.081270257+08:00" level=info msg="Creating a containerd client" address=/run/containerd/containerd.sock timeout=1m0s 7月 08 02:24:59 sw-VMware-Virtual-Platform dockerd[9896]: time="2025-07-08T02:24:59.085148392+08:00" level=info msg="[graphdriver] trying configured driver: overlay2" 7月 08 02:24:59 sw-VMware-Virtual-Platform dockerd[9896]: failed to start daemon: error initializing graphdriver: overlay2: unknown option overlay2.override_kernel_check: overlay2 7月 08 02:24:59 sw-VMware-Virtual-Platform systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE 7月 08 02:24:59 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:24:59 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine. 7月 08 02:25:01 sw-VMware-Virtual-Platform systemd[1]: docker.service: Scheduled restart job, restart counter is at 1. 7月 08 02:25:01 sw-VMware-Virtual-Platform systemd[1]: Starting docker.service - Docker Application Container Engine... 7月 08 02:25:01 sw-VMware-Virtual-Platform dockerd[9921]: time="2025-07-08T02:25:01.171214902+08:00" level=info msg="Starting up" 7月 08 02:25:01 sw-VMware-Virtual-Platform dockerd[9921]: time="2025-07-08T02:25:01.172077051+08:00" level=info msg="OTEL tracing is not configured, using no-op tracer provider" 7月 08 02:25:01 sw-VMware-Virtual-Platform dockerd[9921]: time="2025-07-08T02:25:01.172140193+08:00" level=info msg="CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory" dir=/etc/cdi 7月 08 02:25:01 sw-VMware-Virtual-Platform dockerd[9921]: time="2025-07-08T02:25:01.172147872+08:00" level=info msg="CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory" dir=/var/run/cdi 7月 08 02:25:01 sw-VMware-Virtual-Platform dockerd[9921]: time="2025-07-08T02:25:01.172218780+08:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf" 7月 08 02:25:01 sw-VMware-Virtual-Platform dockerd[9921]: time="2025-07-08T02:25:01.179261467+08:00" level=info msg="Creating a containerd client" address=/run/containerd/containerd.sock timeout=1m0s 7月 08 02:25:01 sw-VMware-Virtual-Platform dockerd[9921]: time="2025-07-08T02:25:01.182966252+08:00" level=info msg="[graphdriver] trying configured driver: overlay2" 7月 08 02:25:01 sw-VMware-Virtual-Platform dockerd[9921]: failed to start daemon: error initializing graphdriver: overlay2: unknown option overlay2.override_kernel_check: overlay2 7月 08 02:25:01 sw-VMware-Virtual-Platform systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE 7月 08 02:25:01 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:25:01 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine. 7月 08 02:25:03 sw-VMware-Virtual-Platform systemd[1]: docker.service: Scheduled restart job, restart counter is at 2. 7月 08 02:25:03 sw-VMware-Virtual-Platform systemd[1]: Starting docker.service - Docker Application Container Engine... 7月 08 02:25:03 sw-VMware-Virtual-Platform dockerd[9948]: time="2025-07-08T02:25:03.449723946+08:00" level=info msg="Starting up" 7月 08 02:25:03 sw-VMware-Virtual-Platform dockerd[9948]: time="2025-07-08T02:25:03.450205624+08:00" level=info msg="OTEL tracing is not configured, using no-op tracer provider" 7月 08 02:25:03 sw-VMware-Virtual-Platform dockerd[9948]: time="2025-07-08T02:25:03.450251582+08:00" level=info msg="CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory" dir=/etc/cdi 7月 08 02:25:03 sw-VMware-Virtual-Platform dockerd[9948]: time="2025-07-08T02:25:03.450257899+08:00" level=info msg="CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory" dir=/var/run/cdi 7月 08 02:25:03 sw-VMware-Virtual-Platform dockerd[9948]: time="2025-07-08T02:25:03.450312061+08:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf" 7月 08 02:25:03 sw-VMware-Virtual-Platform dockerd[9948]: time="2025-07-08T02:25:03.457317190+08:00" level=info msg="Creating a containerd client" address=/run/containerd/containerd.sock timeout=1m0s 7月 08 02:25:03 sw-VMware-Virtual-Platform dockerd[9948]: time="2025-07-08T02:25:03.461180740+08:00" level=info msg="[graphdriver] trying configured driver: overlay2" 7月 08 02:25:03 sw-VMware-Virtual-Platform dockerd[9948]: failed to start daemon: error initializing graphdriver: overlay2: unknown option overlay2.override_kernel_check: overlay2 7月 08 02:25:03 sw-VMware-Virtual-Platform systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE 7月 08 02:25:03 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:25:03 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine. 7月 08 02:25:05 sw-VMware-Virtual-Platform systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. 7月 08 02:25:05 sw-VMware-Virtual-Platform systemd[1]: docker.service: Start request repeated too quickly. 7月 08 02:25:05 sw-VMware-Virtual-Platform systemd[1]: docker.service: Failed with result 'exit-code'. 7月 08 02:25:05 sw-VMware-Virtual-Platform systemd[1]: Failed to start docker.service - Docker Application Container Engine.
最新发布
07-09
在02:24:59和02:25:01等时间的日志中，Docker启动失败的原因是：`failed to start daemon: error initializing graphdriver: overlay2: unknown option overlay2.override_kernel_check: overlay2` 这表明在配置...
centos7下docker启动失败--ob for docker.service failed because the control process exited with error code.
liuchuanliang的博客
11-02 7940
今天在配置openshift用docker部署镜像的时候，启动docker发现竟然启动失败：     之前是可以启动的，突然不能启动了，想到我改了配置文件： 执行： vim /etc/sysconfig/docker 可能是家的内容有问题，删除添加内容如下： 然后再次启动，发现启动成功！ ...
Minio rpm安装后，启动失败。报：Job for minio.service failed because the control process exited with error code
yilvi的博客
12-28 6368
【代码】Minio rpm安装后，启动失败。报：Job for minio.service failed because the control process exited with error code。
Your push failed because you've exceeded your user limit, and this repository is restricted to read-
小歲月丶太着急
08-08 780
公司使用的Bitbucket 免费仓库，一直在正常使用，然后突然就无法push了，提示： Your push failed because you’ve exceeded your user limit, and this repository is restricted to read-only access. 根据提示，一直以为是仓库设置为了只读权限，然后各种调，最后才发现，原来是因为免费...
Docker启动失败问题解决：Job for docker.service failed because the control process exited with error code.....
热门推荐
博客主要分享技术教程、工具教程、bug解决、前沿技术动态、编程经验、心得感悟等。 内容同步、干货获取、推广宣发请看侧栏推广信息
01-31 2万+
每个人都有惰性，但不断学习是好好生活的根本，共勉！
docker启动报错：Job for docker. service failed because the control process exited with error code
2301_76462180的博客
01-18 3451
3、通过命令进入到etc/docker目录下,查看有无daemon.json,这个文件是我们在安装时创建的;5、重新启动docker 就可以了；1、docker状态为关闭。2、启动docker失败。
【服务器】服务器的服务启动失败
Hello World！
08-01 2329
错误 在编辑文件的时候遇到错误： E297: write error in swap file 启动Mariadb服务失败，提示错误： Job for mariadb.service failed because a configured resource limit was exceeded. See “systemctl status mariadb.service” and “journa...
2021-07-08 启动MySQL报错Job for mysqld.service failed because of unavailable resources or another system
weixin_45695857的博客
07-26 1364
启动MySQL报错Job for mysqld.service failed because of unavailable resources or another system error. See "systemc… 不管三七二十一先从mysql 日志文件开找 cat /var/log/mysqld.log 别忘了linux也会 Disk is full writing(磁盘写满) 居然是因为磁盘满了无法启动MySQL,找到问题就好解决了 Filesystem 1K-blocks
Job for docker.service failed because the control process exited with error code. See “systemctl sta
王某Fly的博客
07-26 335
Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details. 设置完daocloud报错 看了下 /etc/docker/daemon.json 因为设置daocloud实际上是修改了/etc/docker/daemon.json这个文件，所以有可能是这个文件有问题
elasticsearch绑定ip
柠檬说葡萄你好酸
11-27 517
看到网上很多方案，不尽详细 官方网络配置地址 有防火墙或者安全组的记得放通9200这个端口，例如阿里云或腾讯云等 network.host: 0.0.0.0 discovery.seed_hosts: ["0.0.0.0"] 要同时配置这两项
inode耗尽导致的nginx无法访问问题
chishi0713的博客
08-20 625
公司有一台测试服务器，部署了非常多的测试服务。某天同事发现部署的测试站点拒绝访问。通过多伦排查，最终确认是由于inode导致nginx无法正常提供服务，并且无法重新启动。 排查过程 确认问题。部署的站点拒绝访问，curl localhost也拒绝访问，应该不是安全策略问题。 检查nginx。...
解决docker启动报错：Job for docker.service failed because the control process exited with error code
10-16
这个错误可能是由于docker服务无法启动导致的。可以尝试以下几个步骤来解决这个问题： 1. 检查docker服务是否已经安装并且正在运行。可以使用以下命令检查docker服务的状态： ``` systemctl status docker ``` 如果docker服务没有运行，可以使用以下命令启动docker服务： ``` systemctl start docker ``` 2. 如果docker服务已经在运行，可以尝试重启docker服务： ``` systemctl restart docker ``` 3. 如果以上步骤都无法解决问题，可以尝试卸载并重新安装docker服务。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值