You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
W0501 18:19:25.711867 15500 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\ASUS.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
minikube v1.33.0 on Microsoft Windows 10 Home 10.0.19045.4291 Build 19045.4291
Kubernetes 1.30.0 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.30.0
Using the docker driver based on existing profile
Starting "minikube" primary control-plane node in "minikube" cluster
Pulling base image v0.0.43 ...
Updating the running docker "minikube" container ...
! 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.32.0 -> Actual minikube version: v1.33.0
Preparing Kubernetes v1.28.3 on Docker 24.0.7 ...| Bad local forwarding specification '0:localhost:8443'
! Unable to restart control-plane node(s), will reset cluster:
Generating certificates and keys ...
Booting up control plane ...
Configuring RBAC rules ...
Configuring bridge CNI (Container Networking Interface) ...
Bad local forwarding specification '0:localhost:8443'
X Exiting due to GUEST_START: failed to start node: Failed kubeconfig update: decode kubeconfig from "C:\Users\ASUS\.kube\config": decode data: : yaml: control characters are not allowed
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │
│
Attach the log file
W0501 18:19:25.711867 15500 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\ASUS.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
minikube v1.33.0 on Microsoft Windows 10 Home 10.0.19045.4291 Build 19045.4291
Kubernetes 1.30.0 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.30.0
Using the docker driver based on existing profile
Starting "minikube" primary control-plane node in "minikube" cluster
Pulling base image v0.0.43 ...
Updating the running docker "minikube" container ...
! 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.32.0 -> Actual minikube version: v1.33.0
Preparing Kubernetes v1.28.3 on Docker 24.0.7 ...| Bad local forwarding specification '0:localhost:8443'
! Unable to restart control-plane node(s), will reset cluster:
Generating certificates and keys ...
Booting up control plane ...
Configuring RBAC rules ...
Configuring bridge CNI (Container Networking Interface) ...
Bad local forwarding specification '0:localhost:8443'
X Exiting due to GUEST_START: failed to start node: Failed kubeconfig update: decode kubeconfig from "C:\Users\ASUS\.kube\config": decode data: : yaml: control characters are not allowed
*
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │
│
Operating System
Windows
Driver
Docker
The text was updated successfully, but these errors were encountered:
What Happened?
W0501 18:19:25.711867 15500 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\ASUS.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
! 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.32.0 -> Actual minikube version: v1.33.0
! Unable to restart control-plane node(s), will reset cluster:
Bad local forwarding specification '0:localhost:8443'
X Exiting due to GUEST_START: failed to start node: Failed kubeconfig update: decode kubeconfig from "C:\Users\ASUS\.kube\config": decode data: : yaml: control characters are not allowed
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run
minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. ││
Attach the log file
W0501 18:19:25.711867 15500 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\ASUS.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
! 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.32.0 -> Actual minikube version: v1.33.0
! Unable to restart control-plane node(s), will reset cluster:
Bad local forwarding specification '0:localhost:8443'
X Exiting due to GUEST_START: failed to start node: Failed kubeconfig update: decode kubeconfig from "C:\Users\ASUS\.kube\config": decode data: : yaml: control characters are not allowed
*
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run
minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. ││
Operating System
Windows
Driver
Docker
The text was updated successfully, but these errors were encountered: