"minikube start" refuses to start (some type of version issue regarding 1.18.3, which has never been installed)

kubernetes / minikube

Run Kubernetes locally

https://minikube.sigs.k8s.io/

Apache License 2.0

29.43k stars 4.88k forks source link

"minikube start" refuses to start (some type of version issue regarding 1.18.3, which has never been installed) #19060

Open davidmpatterson opened 4 months ago

davidmpatterson commented 4 months ago

What Happened?

As above, installation of minikube was normal (I installed 1.33.1). The first startup failed with the error:

Specified Kubernetes version 1.18.3 is less than the oldest supported version: v1.20.0. Use minikube config defaults kubernetes-version for details. ❗ You can force an unsupported Kubernetes version via the --force flag

❌ Exiting due to K8S_OLD_UNSUPPORTED: Kubernetes 1.18.3 is not supported by this release of minikube

The issue is that I've never installed 1.18.3.

Attach the log file

See above.

Operating System

macOS (Default)

Driver

None

sahasouravcse commented 4 months ago

Hi @davidmpatterson , I tried replicating your scenario

Here is my approach -

try minikube delete followed by start --vm-driver=virtualbox then minikube start --vm-driver=virtualbox

eventually minikube status Should get you this

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 3 weeks ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten