繁体   English   中英

kubelet 和 apriserver 因 minikube 而停止

[英]kubelet and apriserver stopped with minikube

我是 Kube.netes 的新手。我试图在我的本地机器上玩 minikube。 我已经在本地安装了 kubectl 和 minikube。 当我跑步时

minikube start --vm-driver=virtualbox # and then 
minikube status

我的 output 是

E0512 23:33:45.964815   23423 status.go:233] kubeconfig endpoint: extract IP: "minikube" 
does not appear in  /.kube/config
m01
host: Running
kubelet: Stopped
apiserver: Stopped
kubeconfig: Misconfigured
WARNING: Your kubectl is pointing to stale minikube-vm. 
To fix the kubectl context, run `minikube update-context`

当我运行minikube update-context时, output 是

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x148ecb0]
..... and more 

有人可以帮忙吗? 提前致谢

按此顺序尝试这些命令:

  1. minikube 站
  2. minikube 删除
  3. minikube 启动

这对我有用

我关闭了我的笔记本电脑,我在虚拟盒子中运行了 minikube。

当我重新启动笔记本电脑并在虚拟盒界面中运行 minikube vm 时,kubelet 和 apiserver 显示已停止。

然后我不得不停止并从 cli 启动 minkube 并发布这两个服务开始出现。

以前>>>

PS C:\Users\mazumdar> minikube status
minikube
type: Control Plane
host: Running
kubelet: Stopped
apiserver: Stopped
kubeconfig: Configured
timeToStop: Nonexistent

发表文章>>>>>>

PS C:\Users\mazumdar> minikube stop
* Stopping node "minikube"  ...
* 1 nodes stopped.
PS C:\Users\mazumdar>
PS C:\Users\mazumdar>
PS C:\Users\mazumdar> minikube start
* minikube v1.18.1 on Microsoft Windows 10 
* Using the virtualbox driver based on existing profile
* Starting control plane node minikube in cluster minikube
* Restarting existing virtualbox VM for "minikube" ...
* Preparing Kubernetes v1.20.2 on Docker 20.10.3 ...
* Verifying Kubernetes components...
  - Using image gcr.io/k8s-minikube/storage-provisioner:v4
* Enabled addons: storage-provisioner, default-storageclass
* Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
PS C:\Users\mazumdar>
PS C:\Users\mazumdar>
PS C:\Users\mazumdar> minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
timeToStop: Nonexistent

当 kubeconfig 配置错误时会发生这种情况。 所以你需要导出 kubeconfig 路径,然后启动 minikube

export KUBECONFIG=$HOME/.kube/config

echo 'export KUBECONFIG=$HOME/.kube/config' >> $HOME/.bashrc

minikube start

minikube status

我正在使用 ubuntu 21.10(内核 - 5.13.0-37-generic)

我用过 minikube stop minikube start

它重新启动了我现有的 minikube 主机

如果我们包含 minikube delete,它将停止并删除现有的 minikube 主机,并在执行“minikube start”时创建一个新主机。

 praba@prabasden:**~$ minikube stop** ✋ Stopping node "minikube"...strong text 1 node stopped. praba@prabasden:**~$ minikube start** minikube v1.25.2 on Ubuntu 21.10 ✨ Using the kvm2 driver based on existing profile Starting control plane node minikube in cluster minikube Restarting existing kvm2 VM for "minikube"... Preparing Kube.netes v1.23.3 on Docker 20.10.12... ▪ kubelet.housekeeping-interval=5m Verifying Kube.netes components... ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5 Enabled addons: storage-provisioner, default-storageclass Done: kubectl is now configured to use "minikube" cluster and "default" namespace by default praba@prabasden:**~$ minikube status** minikube type: Control Plane host: Running kubelet: Running apiserver: Running kubeconfig: Configured

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM