k8s系列：解决start request repeated too quickly for docker.service

最新推荐文章于 2023-09-07 11:20:26 发布
原创 最新推荐文章于 2023-09-07 11:20:26 发布 · 1.8w 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍了如何解决Docker服务启动时遇到的'start request repeated too quickly for docker.service'错误。该问题通常由docker.service失败并进入启动限制导致。通过查看systemd状态和journalctl日志，发现启动请求重复过快。解决方案是检查并修复/etc/docker/daemon.json配置文件中的非法字符或非英文格式的空格。

 

[root@xdoctorx-7008 ~]# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Fri 2020-04-17 21:17:58 CST; 1min 0s ago
     Docs: https://docs.docker.com
  Process: 7243 ExecStart=/usr/bin/dockerd -H unix:// (code=exited, status=1/FAILURE)
 Main PID: 7243 (code=exited, status=1/FAILURE)

Apr 17 21:17:56 master systemd[1]: docker.service: main process exited, cod...RE
Apr 17 21:17:56 master systemd[1]: Failed to start Docker Application Conta...e.
Apr 17 21:17:56 master systemd[1]: Unit docker.service entered fail

了解本专栏 订阅专栏 解锁全文 超级会员免费看
【docker】第10篇 Failed with result ‘exit-code和Start request repeated too quickly和Failed to start Docker
Fanjufei的博客
03-31 6509
【docker】解决 Failed with result 'exit-code'和Start request repeated too quickly和Failed to start Docker。
重启osd服务失败：Start request repeated too quickly
热门推荐
添经地翼的博客
03-20 4万+
背景　　OS：Ubuntu 16.04 　　修改了osd的一些配置，修改后，需要重启osd服务才能生效。第一次重启后，配置立刻生效。再改了一些配置，重启osd服务后，配置却不再生效了。ps命令查看进程，发现osd进程都没有启动。 分析　　osd进程未启动，第一直觉就是配置出错，osd进程启动后又挂掉。于是，进入/var/log/ceph目录，查看ceph-osd.0.log，发现日志末尾只有关闭
部署k8s从节点之后无法启动
运维仙人
09-13 1274
部署k8s从节点之后无法启动 报错：“start request repeated too quickly for kubelet.service” 解决方法： 1、关闭交换分区 swapoff -a 2、 vim /usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf 注释掉红框内的两行 3、执行：systemctl daemon-reload；systemctl start kubelet.service ...
lightdm .service: Start request repeated too quickly. grub正常，不显示登录和桌面 Endeavour
Kearney
11-12 2999
前一天晚上写完代码提示有更新，就浅浅的更新了一下，提示要重启，我就把代码push了重启就出现了上面的情况，有了 sddm 卡死的经历猜测是类似的问题，于是查看 lightdm 的状态，得到关键原因 - lightmdm 没有正常启动。启动界面 grub 正常显示，进入系统后会有代码提示启动了啥，但是最后停在了这个界面，没有转到桌面进行登录，可以切换到 tty2 进行操作。启动项问题：上一次正常启动到这一次不正常启动，我给了 docker 加了开机自启，关掉无效；当时也十点多了，要坐公交回宿舍，感觉把。
Error about “systemd: XXX.service Start request repeated too quickly“ Failed to start
Aaron_Zhang939的博客
09-07 991
!...Restart=......
start request repeated too quickly for filebeat.service
qq_43606931的博客
01-12 3172
最近将FileBeat从主数据中心copy到其他数据中心，修改了配置之后，启动不起来。 systemctl start filebeat 的启动方式报错 "start request repeated too quickly for filebeat.service" 然后，就只好把systemd里的命令拿出来尝试启动了一下 /usr/local/filebeat/filebeat -c /usr/local/filebeat/filebeat.yml -path.home /usr/local
start request repeated too quickly for docker.service
cherish_heart的博客
07-06 2842
docker 问题：start request repeated too quickly for docker.service1、查看具体报错信息 2、docker 服务重启 systemctl restart docker 3、journal -xe 4、检查 /etc/docker/daemon.json 该配置文件中存在非法字符，要注意docker的/etc/docker/daemon.json文件格式，是json格式，千万不能写错，否则docker服务是起不来的。docker 镜像 docker
May 19 10:26:29 k8s-master systemd[1]: Failed to start Docker Application Container Engine. May 19 10:26:29 k8s-master systemd[1]: Unit docker.service entered failed state. May 19 10:26:29 k8s-master systemd[1]: docker.service failed. May 19 10:26:29 k8s-master systemd[1]: docker.service holdoff time over, scheduling restart. May 19 10:26:29 k8s-master systemd[1]: Stopped Docker Application Container Engine. May 19 10:26:29 k8s-master systemd[1]: start request repeated too quickly for docker.service May 19 10:26:29 k8s-master systemd[1]: Failed to start Docker Application Container Engine. May 19 10:26:29 k8s-master systemd[1]: Unit docker.service entered failed state. May 19 10:26:29 k8s-master systemd[1]: docker.service failed.
05-20
例如内存不足或进程数受限等情况可能导致类似报错：“Job for docker.service failed because start of the service was attempted too often.” 此类问题可通过调整以下参数缓解： - 编辑 `/etc/security/limits....
[root@localhost ~]# sudo systemctl status docker.service -l ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since 六 2025-06-14 17:33:17 CST; 1min 25s ago Docs: https://docs.docker.com Process: 98871 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE) Main PID: 98871 (code=exited, status=1/FAILURE) 6月 14 17:33:15 localhost systemd[1]: Failed to start Docker Application Container Engine. 6月 14 17:33:15 localhost systemd[1]: Unit docker.service entered failed state. 6月 14 17:33:15 localhost systemd[1]: docker.service failed. 6月 14 17:33:17 localhost systemd[1]: docker.service holdoff time over, scheduling restart. 6月 14 17:33:17 localhost systemd[1]: Stopped Docker Application Container Engine. 6月 14 17:33:17 localhost systemd[1]: start request repeated too quickly for docker.service 6月 14 17:33:17 localhost systemd[1]: Failed to start Docker Application Container Engine. 6月 14 17:33:17 localhost systemd[1]: Unit docker.service entered failed state. 6月 14 17:33:17 localhost systemd[1]: docker.service failed. [root@localhost ~]# sudo journalctl -xe -u docker.service --since "5 minutes ago" -- -- Unit docker.service has failed. -- -- The result is failed. 6月 14 17:33:12 localhost systemd[1]: Unit docker.service entered failed state. 6月 14 17:33:12 localhost systemd[1]: docker.service failed. 6月 14 17:33:15 localhost systemd[1]: docker.service holdoff time over, scheduling restart. 6月 14 17:33:15 localhost systemd[1]: Stopped Docker Application Container Engine. -- Subject: Unit docker.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has finished shutting down. 6月 14 17:33:15 localhost systemd[1]: Starting Docker Application Container Engine... -- Subject: Unit docker.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has begun starting up. 6月 14 17:33:15 localhost dockerd[98871]: unable to configure the Docker daemon with file /etc/docker/daemon.json: 6月 14 17:33:15 localhost systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE 6月 14 17:33:15 localhost systemd[1]: Failed to start Docker Application Container Engine. -- Subject: Unit docker.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has failed. -- -- The result is failed. 6月 14 17:33:15 localhost systemd[1]: Unit docker.service entered failed state. 6月 14 17:33:15 localhost systemd[1]: docker.service failed. 6月 14 17:33:17 localhost systemd[1]: docker.service holdoff time over, scheduling restart. 6月 14 17:33:17 localhost systemd[1]: Stopped Docker Application Container Engine. -- Subject: Unit docker.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has finished shutting down. 6月 14 17:33:17 localhost systemd[1]: start request repeated too quickly for docker.service 6月 14 17:33:17 localhost systemd[1]: Failed to start Docker Application Container Engine. -- Subject: Unit docker.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has failed. -- -- The result is failed. 6月 14 17:33:17 localhost systemd[1]: Unit docker.service entered failed state. 6月 14 17:33:17 localhost systemd[1]: docker.service failed.
最新发布
06-15
sudo journalctl -u docker.service -b --no-pager -n 100 | grep -i "error\|fail" ``` - 重点关注包含 `daemon.json` 或 `config` 的错误行 3. **验证配置兼容性** ```bash dockerd --validate --config-...
6月 04 21:42:14 k8s01-master01 systemd[1]: docker.service: Start request repeated too quickly. 6月 04 21:42:14 k8s01-master01 systemd[1]: docker.service: Failed with result 'exit-code'. 6月 04 21:42:14 k8s01-master01 systemd[1]: Failed to start Docker Application Container Engine.
06-05
Docker服务在systemd下启动失败，错误代码为`start request repeated too quickly`和`exit-code`，通常表明Docker服务在启动过程中遇到了问题，并且系统尝试重新启动服务的频率过高，导致systemd阻止了进一步的启动...
6月 04 22:02:00 k8s01-master01 systemd[1]: docker.service: Start request repeated too quickly. 6月 04 22:02:00 k8s01-master01 systemd[1]: docker.service: Failed with result 'exit-code'. 6月 04 22:02:00 k8s01-master01 systemd[1]: Failed to start Docker Application Container Engine.
06-06
Docker 服务启动失败，错误信息为 `start request repeated too quickly` 和 `failed with result exit-code`，通常表明 Docker 的核心组件在初始化时遇到了问题。以下是可能的原因及对应的解决方案。 #### 1. 检查...
start request repeated too quickly for syslog-ng.service
heidas的专栏
01-28 3991
If you use ‘unix-stream (“/dev/log”)’ in one of your log messages sources, you will need to manually change it to ‘unix-dgram (“/dev/log”)’.
TS：解决docker无法启动，报：start request repeated too quickly for docker.service错误-2021.12.08(已解决)
weixin_39246554的博客
12-08 3万+
目录 文章目录目录1、报错现象2、解决办法3、总结关于我最后 1、报错现象 首先，我当前的环境是：docker 20.10.11,vmworkstation虚机 很奇怪，自己的docker用着用着就出现问题了，查看服务发现起不来，重启docker服务也不行，重启机器也不行。(呵呵，最后发现还是自己误配置了……????)，这边我们来再具体一步步来排查先这个问题。 step1：查看当前的docker服务状态及报错现象： systemctl status docker step2：查看docker服务状态发现d
Start request repeated too quickly解决方法
qq_20243873的博客
07-10 4万+
脚本重启时间太快，不清楚是什么原因。可能是默认的重启时间为0.1秒。 可以添加StartLimitInterval=600，600表示600秒。 [Unit] Description=ddns [Service] ExecStart=/usr/bin/python3 /usr/ddns/aliddns.py # 可执行文件路径 WorkingDirectory=/usr/ddns/ #工作目录 Restart=always StartLimitInterval=600 [Install] Wa
新机部署docker报错docker.service: Start request repeated too quickly.
dorlolo的博客
04-30 1万+
报错内容 主要报错内容 docker.service: Start request repeated too quickly. Failed with result 'exit-code'. Failed to start Docker Application Container Engine. 判断思路与方案 首先这是新安装的docker，不太可能有问题。想起来刚才修改了deamon.json文件。查看了一下 vim /etc/docker/daemon.json 内容如下 { "re
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

NIO4444

如果对您有帮助，欢迎打赏支持！

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值