pod状态一直ContainerCreating
来源:6-3 边缘侧数据持久化

椰啵啵
2023-03-21
egecore已经配置了podsandboxImage
"RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to get sandbox image \"k8s.gcr.io/pause:3.5\": failed to pull image \"k8s.gcr.io/pause:3.5\": failed to pull and unpack image \"k8s.gcr.io/pause:3.5\": failed to resolve reference \"k8s.gcr.io/pause:3.5\": failed to do request: Head \"https://k8s.gcr.io/v2/pause/manifests/3.5\": dial tcp 74.125.204.82:443: connect: connection refused"
worker [0] handle pod addition item [nginx-deployment-74754f9cc5-c49nl] failed: failed to "CreatePodSandbox" for "nginx-deployment-74754f9cc5-c49nl_default(094bf6a1-6952-4cf4-a09e-ab572b7334fd)" with CreatePodSandboxError: "Failed to create sandbox for pod \"nginx-deployment-74754f9cc5-c49nl_default(094bf6a1-6952-4cf4-a09e-ab572b7334fd)\": rpc error: code = Unknown desc = failed to get sandbox image \"k8s.gcr.io/pause:3.5\": failed to pull image \"k8s.gcr.io/pause:3.5\": failed to pull and unpack image \"k8s.gcr.io/pause:3.5\": failed to resolve reference \"k8s.gcr.io/pause:3.5\": failed to do request: Head \"https://k8s.gcr.io/v2/pause/manifests/3.5\": dial tcp 74.125.204.82:443: connect: connection refused", re-add to queue
Warning MissingClusterDNS kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to "Default" policy.
dial wss://127.0.0.1:10004/v1/kubeedge/connect error dial tcp 127.0.0.1:10004: connect: connection refused
1回答
-
暮闲
2023-03-25
docker容器运行时的问题,配置运行时为docker可解决。00
相似问题