kubelet 和 apriserver 因 minikube 而停止

Question

我是 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 

有人可以幫忙嗎？ 提前致謝

Answer 1

按此順序嘗試這些命令：

1. minikube 站
2. minikube 刪除
3. minikube 啟動

這對我有用

Answer 2

我關閉了我的筆記本電腦，我在虛擬盒子中運行了 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

Answer 3

當 kubeconfig 配置錯誤時會發生這種情況。 所以你需要導出 kubeconfig 路徑，然后啟動 minikube

export KUBECONFIG=$HOME/.kube/config

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

minikube start

minikube status

Answer 4

我正在使用 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