What happened : Initating the minikue minikube start , but it show an error Starting local Kubernetes v1. Starting VM Getting VM IP address Moving files into cluster E What you expected to happen : virtualbox has to start normally but did not happen so it displayed this.
Output of minikube logs if applicable : Dec 04 minikube kubelet[]: E Anything else do we need to know : I have tried solutions which are posted in other site from google and other blogs but its was not successfully.
The text was updated successfully, but these errors were encountered:. If I'm interpreting this properly, some other process killed the ssh or underlying scp process with kill Any clue what that might have been? Scouring stack overflow solutions for similar problems did not resolve my issue, so hoping to share what I'm currently experiencing to get help debugging this. I went ahead and tried following the minikube tutorial today and am now experiencing issues.
I'm following the minikube getting started guide. I don't know what happened, but checking the status again returned "Misconfigured". Double-checked context and I'm still using "minikube" both for context and cluster:.
Reading github issues, I ran into this one: kubernetes Often fixes strange minikube problems. Stale issues rot after an additional 30d of inactivity and eventually close. Sorry, something went wrong. Starting VM Getting VM IP address Moving files into cluster E My best guess here is that VirtualBox stopped the guest VM in the middle of the scp transfer. If you encounter this again, please attach the output of the following commands to this bug:.
Stale issues rot after 30d of inactivity. Rotten issues close after an additional 30d of inactivity. Rotten issues close after 30d of inactivity. In response to this :. Instructions for interacting with me using PR comments are available here.
0コメント