0.31.0 start throws E1212 19:15:18.580331 25180 start.go:210] Error parsing version semver: Version string empty #3447
Comments
|
I am getting the same error message on Mac with minikube v0.31.0 and hyperkit v0.20180403-17-g3e954c |
|
Getting this on macOS too. |
|
Same problem. Windows 10 Enterprise. And unlike the OP, my start is hanging trying to download kubelet and kubeadm. No VirtualBox VM is being created (all though a host adapter was created)
Update: I "fixed" the problem by downgrading to Minikube 0.30.0. There seems to be problems with the 0.31.0 version. This may or may not be related - #3437. minikube start failed the first time with errors on VM. So I deleted the VM (which wasn't visible in VirtualBox) using minikube delete. I still can't see the VM in VirtualBox. But that looks like a VirtualBox issue. I added it manually using C:\Dev\Kubernetes.minikube\machines\minikube\minikube\minikube.vbox. But it always shows as Powered Off even when Minikube is started. So no real point in adding it manually. |
|
Same problem. Windows 10 Enterprise. |
|
I am getting the same error
output |
|
Same issue. But minikube is running correctly |
balopat
added
ev/hung-start
kind/bug
|
This seems to be a red herring - not sure exactly yet how this situation turns up but I just had it on my machine too. I checked |
|
Got it - ed8f712#diff-ed78cd81495af3964aba5fbc898c33a2R164 @priyawadhwa can you have a look at this, please? |
In PR kubernetes#3426, I changed "minikube start" to overwrite the cluster config earlier so that the container runtime could be extracted from it by the buildroot provisioner. This introduced a bug later on, where minikube expected to read the kubernetes version from theold config (which no longer existed, because the config was overwritten). To fix this, I changed the code to store the old version of the config in memory before overwriting it. This should fix kubernetes#3447
|
@balopat this happens to me consistently on macOS with minikube v0.31.0 when trying to boot up a v1.13.0 K8S cluster. |
|
@alexsomesan minikube was overwriting the config file on "minikube start" which caused this error to log, #3450 should fix it once merged |
|
Thanks, that makes my day sunnier. I'll watch #3450 then. |
* Save old cluster config in memory before overwriting In PR #3426, I changed "minikube start" to overwrite the cluster config earlier so that the container runtime could be extracted from it by the buildroot provisioner. This introduced a bug later on, where minikube expected to read the kubernetes version from theold config (which no longer existed, because the config was overwritten). To fix this, I changed the code to store the old version of the config in memory before overwriting it. This should fix #3447
0.31.0 start throws E1212 19:15:18.580331 25180 start.go:210] Error parsing version semver: Version string empty but installation is successful on windows with virtualbox. what is was that error ?
C:\Users\ss\Desktop>minikube-windows-amd64.exe start
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Downloading Minikube ISO
178.87 MB / 178.87 MB [============================================] 100.00% 0s
Getting VM IP address...
E1212 19:15:18.580331 25180 start.go:210] Error parsing version semver: Version string empty
Moving files into cluster...
Downloading kubelet v1.10.0
Downloading kubeadm v1.10.0
Finished Downloading kubeadm v1.10.0
Finished Downloading kubelet v1.10.0
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Stopping extra container runtimes...
Starting cluster components...
Verifying kubelet health ...
Verifying apiserver health ...Kubectl is now configured to use the cluster.
Loading cached images from config file.
Everything looks great. Please enjoy minikube!
Please provide the following details:
Environment:
Minikube version (use
minikube version):cat ~/.minikube/machines/minikube/config.json | grep DriverName):virtualboxcat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION):v0.31.0.iso",The text was updated successfully, but these errors were encountered: