【failed to dial “/run/containerd/containerd.sock“: unknown service containerd.services.namespaces.v】

最新推荐文章于 2025-10-02 10:58:35 发布
原创 最新推荐文章于 2025-10-02 10:58:35 发布 · 4.1k 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#docker #kubernetes #容器

在服务器遭遇异常断电后，尝试启动Docker服务时遇到错误，日志显示failedtodial/run/containerd/containerd.sock:unknownservicecontainerd.services.namespaces.v1.Namespaces:notimplemented。按照常规方法如重启containerd和docker服务未解决问题。最终通过直接运行dockerd命令成功启动了Docker服务，解决了启动失败的状况。

failed to dial “/run/containerd/containerd.sock”: unknown service containerd.services.namespaces.v1.Namespaces: not implemented

服务器异常断电后，再去启动docker的时候起不来

[www-admin@k8s-node7 xxxxx]# journalctl -u docker -f
-- Logs begin at Sun 2022-11-06 04:04:40 CST. --
Mar 03 11:08:26 k8s-node7 dockerd[4355]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": unknown service containerd.services.namespaces.v1.Namespaces: not implemented
Mar 03 11:08:26 k8s-node7 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Mar 03 11:08:26 k8s-node7 systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 03 11:08:26 k8s-node7 systemd[1]: Failed to start Docker Application Container Engine.
Mar 03 11:08:28 k8s-node7 systemd[1]: docker.service: Service RestartSec=2s expired, sc
最低0.47元/天 解锁文章
Ms_qsl
关注
Containerd 错误报错解决Failed to start containerd container runtime.
一叶的博客
07-31 2万+
systemctlstatuscontainerd.service发现是无法启动容器运行时。解决方案，删除以前的Containerd配置文件，重新执行一下Containerd的安装过程。镜像加速的配置就在cri插件配置块下面的registry配置块。当安装Containerd，在重启Containerd时出现。排查发现是Containerd启动时配置文件的问题。journalctl-xe查看具体原因如下。启动Containerd，并查询状态。重新执行文章中的安装部分。修改为如下配置文件格式。...
docker实际生产中遇到的问题及解决办法
weixin_38924998的博客
02-05 2280
解决：这里有containerd的目录，需要将/var/lib/docker整个目录删除掉。解决：删除目录 /run/containerd/containerd.sock。
彻底解决Containerd gRPC错误：从原理到实战的容错架构设计
gitblog_01017的博客
10-02 776
你是否遇到过Containerd客户端连接超时却无法定位原因？调用容器API时错误信息模糊不清？本文将系统讲解Containerd的gRPC错误处理机制，通过7个实战技巧和3种高级模式，帮助你构建99.9%可用性的容器管理系统。读完本文你将掌握：错误码映射规则、重试策略设计、命名空间隔离方案以及分布式追踪实现。 ## 错误处理架构概览 Containerd采用双层错误处理架构：底层通过gRPC...
k8s集群某个节点重启之后，不能使用 tab 键，docker启动失败
Small_StarOne的博客
07-18 1342
k8s节点宕机重启，docker、kubelet 启动失败
docker出现 dial unix /run/containerd/containerd.sock: connect: connection refused 解决思路
recotone的专栏
09-12 3411
先说现像，应用突然不能访问了，执行docker exec -it app bash 时就出现了这个错误。显示是：Active: active (running)，但日志中有一句。于是检查Docker的服务状态。
/run/containerd/containerd.sock connect: connection refused
weixin_46941625的博客
09-01 6022
docker
failed to dial gRPC: cannot connect to the Docker daemon
qq_27147201的博客
08-06 9263
出现这个问题一般都是以为没启动docker，犯了一个zz的错误
~ ~ lines 1319-1345/1345 (END) 6月 08 11:48:27 client systemd[1]: docker.service: Start request repeated too quickly. 6月 08 11:48:27 client systemd[1]: docker.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit docker.service has entered the 'failed' state with result 'exit-code'. 6月 08 11:48:27 client systemd[1]: Failed to start Docker Application Container Engine. -- Subject: docker.service 单元已失败 -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- docker.service 单元已失败。 -- -- 结果为“failed”。 6月 08 11:48:27 client systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'. 6月 08 11:48:38 client systemd[1]: systemd-hostnamed.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-hostnamed.service has successfully entered the 'dead' state. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
06-09
在日志中可能会发现与 `containerd` 相关的错误信息，例如 `failed to dial "/run/containerd/containerd.sock": unknown service containerd.services.namespaces.v1.Namespaces: not implemented`。这种情况下，...
-- Logs begin at Sun 2025-06-08 06:57:05 CST, end at Sun 2025-06-08 11:48:38 CST. -- 6月 08 08:03:17 client systemd[1]: Stopping Docker Application Container Engine... 6月 08 08:03:17 client dockerd[14141]: time="2025-06-08T08:03:17.377722185+08:00" level=info msg="Proc> 6月 08 08:03:17 client dockerd[14141]: time="2025-06-08T08:03:17.569744299+08:00" level=info msg="stop> 6月 08 08:03:17 client dockerd[14141]: time="2025-06-08T08:03:17.580670688+08:00" level=info msg="Daem> 6月 08 08:03:17 client systemd[1]: docker.service: Succeeded. 6月 08 08:03:17 client systemd[1]: Stopped Docker Application Container Engine. 6月 08 08:03:17 client systemd[1]: Starting Docker Application Container Engine... 6月 08 08:03:17 client dockerd[19561]: time="2025-06-08T08:03:17.900258455+08:00" level=info msg="Star> 6月 08 08:03:18 client dockerd[19561]: time="2025-06-08T08:03:18.125226708+08:00" level=info msg="[gra> 6月 08 08:03:18 client dockerd[19561]: time="2025-06-08T08:03:18.139846223+08:00" level=info msg="Load> 6月 08 08:03:18 client dockerd[19561]: time="2025-06-08T08:03:18.484917294+08:00" level=info msg="Defa> 6月 08 08:03:18 client dockerd[19561]: time="2025-06-08T08:03:18.607474197+08:00" level=info msg="Load> 6月 08 08:03:18 client dockerd[19561]: time="2025-06-08T08:03:18.638344508+08:00" level=info msg="Dock> 6月 08 08:03:18 client dockerd[19561]: time="2025-06-08T08:03:18.638467523+08:00" level=info msg="Daem> 6月 08 08:03:18 client dockerd[19561]: time="2025-06-08T08:03:18.731501215+08:00" level=info msg="API > 6月 08 08:03:18 client systemd[1]: Started Docker Application Container Engine. 6月 08 08:18:54 client dockerd[19561]: time="2025-06-08T08:18:54.975222171+08:00" level=warning msg="E> 6月 08 08:18:54 client dockerd[19561]: time="2025-06-08T08:18:54.975827380+08:00" level=info msg="Atte> 6月 08 08:18:54 client dockerd[19561]: time="2025-06-08T08:18:54.987448312+08:00" level=error msg="Han> 6月 08 08:19:10 client dockerd[19561]: time="2025-06-08T08:19:10.928262511+08:00" level=warning msg="E> 6月 08 08:19:10 client dockerd[19561]: time="2025-06-08T08:19:10.928362267+08:00" level=info msg="Atte> 6月 08 08:19:10 client
06-09
在日志中可能会发现与 `containerd` 相关的错误信息，例如 `failed to dial "/run/containerd/containerd.sock": unknown service containerd.services.namespaces.v1.Namespaces: not implemented`。这种情况下，...
ode01-49 ~]# sudo kubeadm init \ > --config init-config.yaml \ > --ignore-preflight-errors=NumCPU,Mem \ > --v=5 \ > --timeout=10m unknown flag: --timeout [root@k8snode01-49 ~]# journalctl -u kubelet -n 100 --no-pager -- Logs begin at 三 2025-06-25 09:03:58 CST, end at 三 2025-06-25 14:30:27 CST. -- 6月 25 14:30:18 k8snode01-49 kubelet[12279]: E0625 14:30:18.712037 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:18 k8snode01-49 kubelet[12279]: E0625 14:30:18.812141 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:18 k8snode01-49 kubelet[12279]: E0625 14:30:18.819424 12279 kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized" 6月 25 14:30:18 k8snode01-49 kubelet[12279]: E0625 14:30:18.912896 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:18 k8snode01-49 kubelet[12279]: W0625 14:30:18.935733 12279 reflector.go:424] vendor/k8s.io/client-go/informers/factory.go:134: failed to list *v1.Service: Get "https://cluster-endpoint:6443/api/v1/services?limit=500&resourceVersion=0": dial tcp 192.168.199.149:6443: connect: connection refused 6月 25 14:30:18 k8snode01-49 kubelet[12279]: I0625 14:30:18.936006 12279 trace.go:205] Trace[1191624498]: "Reflector ListAndWatch" name:vendor/k8s.io/client-go/informers/factory.go:134 (25-Jun-2025 14:29:57.882) (total time: 21053ms): 6月 25 14:30:18 k8snode01-49 kubelet[12279]: Trace[1191624498]: ---"Objects listed" error:Get "https://cluster-endpoint:6443/api/v1/services?limit=500&resourceVersion=0": dial tcp 192.168.199.149:6443: connect: connection refused 21053ms (14:30:18.935) 6月 25 14:30:18 k8snode01-49 kubelet[12279]: Trace[1191624498]: [21.053886657s] [21.053886657s] END 6月 25 14:30:18 k8snode01-49 kubelet[12279]: E0625 14:30:18.936041 12279 reflector.go:140] vendor/k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Service: failed to list *v1.Service: Get "https://cluster-endpoint:6443/api/v1/services?limit=500&resourceVersion=0": dial tcp 192.168.199.149:6443: connect: connection refused 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.017806 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.120250 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.221473 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.322337 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.423308 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.524142 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.624475 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.725451 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.827023 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:19 k8snode01-49 kubelet[12279]: E0625 14:30:19.928492 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.028874 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.130464 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.230815 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.331650 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.431927 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.533869 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.634827 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.735758 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.837751 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:20 k8snode01-49 kubelet[12279]: E0625 14:30:20.939432 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.040074 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.140662 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.240926 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.341698 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.443461 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.543736 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.645837 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.746364 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.847381 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:21 k8snode01-49 kubelet[12279]: E0625 14:30:21.947622 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.049652 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.151008 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.252964 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.353278 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.453949 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.555585 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.656765 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.758248 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.858804 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:22 k8snode01-49 kubelet[12279]: E0625 14:30:22.959261 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.059796 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.160271 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.260648 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.361469 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.462024 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.564090 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.664973 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.794363 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.822390 12279 kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.894476 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:23 k8snode01-49 kubelet[12279]: E0625 14:30:23.994915 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.098096 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.198461 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.299238 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.400796 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.501805 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.602759 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.703931 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.804321 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:24 k8snode01-49 kubelet[12279]: E0625 14:30:24.905478 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.005602 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.105697 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.208382 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.308750 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.409347 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.509493 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.609844 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.715544 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.820113 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:25 k8snode01-49 kubelet[12279]: E0625 14:30:25.921365 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.022912 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.124268 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.225609 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.326621 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.431528 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.532019 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.632634 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.733181 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.835721 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.886917 12279 event.go:276] Unable to write event: '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"k8snode01-49.184c34f680dbc2a6", GenerateName:"", Namespace:"default", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeletionTimestamp:<nil>, DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ManagedFields:[]v1.ManagedFieldsEntry(nil)}, InvolvedObject:v1.ObjectReference{Kind:"Node", Namespace:"", Name:"k8snode01-49", UID:"k8snode01-49", APIVersion:"", ResourceVersion:"", FieldPath:""}, Reason:"InvalidDiskCapacity", Message:"invalid capacity 0 on image filesystem", Source:v1.EventSource{Component:"kubelet", Host:"k8snode01-49"}, FirstTimestamp:time.Date(2025, time.June, 25, 14, 23, 8, 468765350, time.Local), LastTimestamp:time.Date(2025, time.June, 25, 14, 23, 8, 468765350, time.Local), Count:1, Type:"Warning", EventTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'Post "https://cluster-endpoint:6443/api/v1/namespaces/default/events": dial tcp 192.168.199.149:6443: connect: connection refused'(may retry after sleeping) 6月 25 14:30:26 k8snode01-49 kubelet[12279]: E0625 14:30:26.952291 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.052833 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.153615 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.254331 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.357955 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.458234 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.559218 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.661101 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.761525 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.862847 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found" 6月 25 14:30:27 k8snode01-49 kubelet[12279]: E0625 14:30:27.963152 12279 kubelet.go:2448] "Error getting node" err="node \"k8snode01-49\" not found"
06-26
> criSocket: unix:///var/run/dockershim.sock > --- > apiVersion: kubeadm.k8s.io/v1beta3 > kind: ClusterConfiguration > networking: > podSubnet: "10.244.0.0/16" # Flannel 所需子网 > ``` --- #### 2. *...
【docker】docker启动失败报错
苦苦思索的吃瓜群众博客
02-24 4521
failed to start daemon: failed to dial "/run/containerd/containerd.sock": unknown service containerd.services.namespaces.v1.Namespaces: not implemented
ubuntu containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
tryyourbest0928的博客
01-04 8117
root@xxktt-System-Product-Name:~# systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2021-0
docker启动失败failed to connect to containerd: could not change group /var/run/docker.sock:group docker
sinat_38653840的博客
02-20 7137
docker启动失败failed to connect to containerd: could not change group /var/run/docker.sock:group docker not found 查找一下发现找不到文件vi /etc/sysconfig/docker 改为：--selinux-enabled=false 解决办法：重新安装docker 1、查看已安...
Failed to connect to containerd: exec: “docker-containerd“: executable file not found in $PATH
qq_44534541的博客
06-09 1768
是我的docker路径。在环境变量中添加参数。
crictl 遇到报错 /run/containerd/containerd.sock: connect: permission denied
gs80140的专栏
04-24 601
crictl --runtime-endpoint unix:///run/containerd/containerd.sock logs CONTAINERID FATA[0000] validate service connection: validate CRI v1 runtime API for endpoint "unix:///run/containerd/containerd.sock": rpc error: code = Unavailable desc = connection err
k8s containerd私有仓库配置及常用命令
热门推荐
qq_39360187的博客
03-11 1万+
修改containerd配置文件，添加私有仓库配置。
Docker启动错误
bare_rain的博客
04-30 3457
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Kubelet CRI 容器运行时 Containerd
小楼一夜听春雨，深巷明朝卖杏花
07-26 1738
如果是通过kubelet去调用docker的话，这个请求是在kubelet的cri接口调用docker-shim，docker-shim再连接到docker-daemon，docker-daemon里面红圈的这部分才是有用的，也就是和image相关的操作，以及正真去去调用containerd的这部分操作是有用的，上面存储网络，已经docker提供的cli这些都是不需要的，那么这些都是冗余的。不再使用docker自身的daemon了，但是可以用你docker自身所带的containerd的。...
【containerd 源码分析】containerd 启动流程分析
zhonglinzhang
08-02 1万+
github:https://github.com/containerd/containerdrelease-v1.3.0 前言 dockerd是docker engine守护进程，dockerd启动时会启动containerd子进程，dockerd与containerd通过rpc进行通信 ctr是containerd的cli containerd通过shim操作runc，r...
Error while dialing: dial unix /var/run/containerd/containerd.sock: connect: no such file or directory
最新发布
10-05
当 containerd 运行时出现 `dial unix /var/run/containerd/containerd.sock: connect: no such file or directory` 错误，可能是由于 containerd 服务未启动、配置文件有误或者相关目录权限问题等原因导致。以下是一些解决方法： ### 检查并启动 containerd 服务 确保 containerd 服务已经启动。可以使用以下命令启动 containerd 服务： ```bash systemctl start containerd ``` 若想让 containerd 服务在系统启动时自动启动，可使用以下命令： ```bash systemctl enable containerd ``` ### 检查配置文件 检查 containerd 的配置文件 `/etc/containerd/config.toml` 是否存在错误。确保配置文件中的 `[grpc]` 部分配置正确，例如： ```toml [grpc] address = "/var/run/containerd/containerd.sock" ``` 若配置文件有修改，需重启 containerd 服务： ```bash systemctl restart containerd ``` ### 检查目录和文件权限 确保 `/var/run/containerd` 目录和 `containerd.sock` 文件的权限设置正确。可以使用以下命令检查和修改权限： ```bash chown -R root:root /var/run/containerd chmod -R 755 /var/run/containerd ``` ### 检查 cgroup 配置 参考之前解决 `cgroups: invalid group path` 问题的方法，确保 cgroup 配置正确，避免因 cgroup 问题导致 containerd 无法正常启动。例如，检查 cgroup 版本并调整运行时，可安装 `crun` 并修改配置文件 `/usr/share/containers/containers.conf` 中的 `runtime` 为 `crun`： ```bash yum -y install crun vi /usr/share/containers/containers.conf # 修改为 runtime = "crun" #runtime = "runc" ``` ### 检查系统日志 使用 `journalctl -u containerd` 命令查看 containerd 的详细日志信息，根据日志中的具体错误信息进行相应的处理： ```bash journalctl -u containerd ```
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值