1
根据官方文档here在Container中本地运行Kubernetes - 我已经仔细地遵循了所有步骤,并且当我输入kubectl get nodes
时,我仍然收到消息connection refused
。Kubernetes(本地Docker方法)是否真的有效?
docker ps
表明API服务器没有运行,并docker logs kubelet
确实varify这样:
[kubelet.go:1137] Unable to register 127.0.0.1 with the apiserver: Post http://localhost:8080/api/v1/nodes: dial tcp 127.0.0.1:8080: connection refused.
一小会儿后,docker logs kubelet
E0711 16:07:06.814735 33792 event.go:202] Unable to write event: 'Post http://localhost:8080/api/v1/namespaces/default/events: dial tcp 127.0.0.1:8080: connection refused' (may retry after sleeping)
很显然,我不是一个人在遇到这个问题。
UPDATE: 几个小时后,docker logs kubelet
E0712 08:28:03.528010 33792 pod_workers.go:138] Error syncing pod 4c6ab43ac4ee970e1f563d76ab3d3ec9, skipping: [failed to "StartContainer" for "controller-manager" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=controller-manager pod=k8s-master-127.0.0.1_default(4c6ab43ac4ee970e1f563d76ab3d3ec9)"
, failed to "StartContainer" for "apiserver" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=apiserver pod=k8s-master-127.0.0.1_default(4c6ab43ac4ee970e1f563d76ab3d3ec9)"
, failed to "StartContainer" for "setup" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=setup pod=k8s-master-127.0.0.1_default(4c6ab43ac4ee970e1f563d76ab3d3ec9)"
]
我试过Minikube,仍然得到相同的问题。我已经更新了(尝试启动api-server容器的日志)。它确实表明容器崩溃。 – nikk
:(令人沮丧的是,'docker logs kubelet'会告诉你kubelet在启动kubernetes容器时试图做什么,我想知道这些容器崩溃的原因是否有剩余日志(比如docker logs apiserver '或什么的) –
不是。'docker logs apiserver' '错误:没有这样的容器:apiserver ' – nikk