Minikube v1.36.0 ISO shows internal version as v1.35.0, causing "Image was not built" warning #20829
Labels
Comments
|
I encounter the same issue on macOS Sequoia (15.5) with vfkit. ❯ minikube version
minikube version: v1.36.0
commit: f8f52f5de11fc6ad8244afac475e1d0f96841df1-dirty
❯ minikube start
😄 minikube v1.36.0 sur Darwin 15.5 (arm64)
✨ Utilisation du pilote vfkit basé sur la configuration de l'utilisateur
👍 Démarrage du nœud "minikube" primary control-plane dans le cluster "minikube"
🔥 Création de VM vfkit (CPUs=4, Mémoire=4096MB, Disque=20480MB)...
❗ L'image n'a pas été construite pour la version actuelle de minikube. Pour résoudre ce problème, vous pouvez supprimer et recréer votre cluster minikube en utilisant les dernières images. Version de minikube attendue : v1.35.0 -> Version de minikube actuelle : v1.36.0
🎁 Préparation de Kubernetes v1.33.1 sur CRI-O 1.29.1...
▪ Génération des certificats et des clés
▪ Démarrage du plan de contrôle ...
▪ Configuration des règles RBAC ...
🔗 Configuration de Cilium (Container Networking Interface)...
🔎 Vérification des composants Kubernetes...
▪ Utilisation de l'image gcr.io/k8s-minikube/minikube-ingress-dns:0.0.3
▪ Utilisation de l'image gcr.io/k8s-minikube/storage-provisioner:v5
▪ Utilisation de l'image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.5.3
▪ Utilisation de l'image registry.k8s.io/ingress-nginx/controller:v1.12.2
▪ Utilisation de l'image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.5.3
🔎 Vérification du module ingress...
🌟 Modules activés: ingress-dns, default-storageclass, storage-provisioner, ingress
🏄 Terminé ! kubectl est maintenant configuré pour utiliser "minikube" cluster et espace de noms "default" par défaut.
❯ minikube ssh "cat /version.json"
{"iso_version": "v1.35.0-1747341198-20771", "kicbase_version": "v0.0.46-1747264594-20764", "minikube_version": "v1.35.0", "commit": "1d2a534581c8e170c41e848d290ed4ff82c01157"} |
|
I experience the same problem on Linux with kvm2 driver $> uname -a
Linux SeiShinGi 6.11.0-114024-tuxedo #24~24.04.1tux1 SMP PREEMPT_DYNAMIC Wed Apr 23 13:23:53 UTC 2025 x86_64 x86_64 x86_64 GNU/LinuxRunning minikube with the following parameters: $> /usr/bin/minikube start \
--driver=kvm2 \
--cpus='6' \
--disable-metrics=true \
--disk-size='90974mb' \
--dns-domain='cluster.local' \
--kubernetes-version='v1.32.0' \
--memory='5170m' \
--nodes=2 \
--container-runtime='containerd' \
--extra-config=kubeadm.pod-network-cidr=10.244.0.0/16 \
--service-cluster-ip-range='10.96.0.0/12' \
--profile='myprofile'I see the same warning and { "iso_version": "v1.35.0-1747341198-20771",
"kicbase_version": "v0.0.46-1747264594-20764",
"minikube_version": "v1.35.0",
"commit": "1d2a534581c8e170c41e848d290ed4ff82c01157"
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What Happened?
Minikube Version:
v1.36.0v1.35.0Operating System:
Driver:
What happened:
After upgrading the Minikube CLI from
v1.35.0tov1.36.0and attempting to create a new cluster (even afterminikube deleteand clearing caches like~/.minikube/cache/and~/.minikube/machines/), I consistently receive the following warning:❗ Image was not built for the current minikube version. To resolve this you can delete and recreate your minikube cluster using the latest images. Expected minikube version: v1.35.0 -> Actual minikube version: v1.36.0
The cluster creation proceeds, and Kubernetes (e.g., v1.33.1) seems to start, but this warning persists.
Diagnosis:
I SSH'd into the Minikube VM (
minikube ssh) created by thev1.36.0CLI and checked the content of/version.json. It reported:{ "iso_version": "v1.35.0-1747341198-20771", "kicbase_version": "v0.0.46-1747264594-20764", "minikube_version": "v1.35.0", "commit": "1d2a534581c8e170c41e848d290ed4ff82c01157" }Attach the log file
log.txt
Operating System
macOS (Default)
Driver
HyperKit
The text was updated successfully, but these errors were encountered: