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
I ran minikube delete --all --purge
I deleted the ~/.minikube directory
But starting a cluster I got this error: minikube start -p mycluster --kubernetes-version=v1.23.14 --driver=docker --force-systemd=true [ERROR KubeletVersion]: couldn't get kubelet version: cannot execute 'kubelet --version': fork/exec /var/lib/minikube/binaries/v1.23.14/kubelet: no such file or directory
I'm at a loss, what else can I try? This is suppose to work after purging but its not for me.
Attach the log file
% minikube logs -p mycluster --file=logs.txt
E0317 11:23:33.593922 85617 logs.go:193] command /bin/bash -c "sudo /var/lib/minikube/binaries/v1.23.14/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig" failed with error: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.23.14/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig": Process exited with status 1
stdout:
stderr:
The connection to the server localhost:8443 was refused - did you specify the right host or port?
output: "\n** stderr ** \nThe connection to the server localhost:8443 was refused - did you specify the right host or port?\n\n** /stderr **"
❗ unable to fetch logs for: describe nodes
There is no /var/lib/minikube folder on my system
Operating System
macOS (Default)
Driver
Docker
The text was updated successfully, but these errors were encountered:
I also had DOCKER_DEFAULT_PLATFORM=linux/amd64 set.
Maybe minikube should be smart enough unset this or pass docker the platform arg specifically?
This is a common setting for users and especially M1 users I'd think because we need to build and run images with the same arch we deploy to production (to test locally consistently).
I would have expected DOCKER_DEFAULT_PLATFORM to only effect my own docker builds. Is minikubet orchestrating the docker cli itself? Curious how this setting is effecting minikube- maybe it effects all docker pulls run from the docker cli or api?
What Happened?
Related #12274
I initially installed via homebrew and got this error.
I uninstalled via brew and reinstall the right arch:
I ran
minikube delete --all --purge
I deleted the
~/.minikube directory
But starting a cluster I got this error:
minikube start -p mycluster --kubernetes-version=v1.23.14 --driver=docker --force-systemd=true
[ERROR KubeletVersion]: couldn't get kubelet version: cannot execute 'kubelet --version': fork/exec /var/lib/minikube/binaries/v1.23.14/kubelet: no such file or directory
I'm at a loss, what else can I try? This is suppose to work after purging but its not for me.
Attach the log file
% minikube logs -p mycluster --file=logs.txt
E0317 11:23:33.593922 85617 logs.go:193] command /bin/bash -c "sudo /var/lib/minikube/binaries/v1.23.14/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig" failed with error: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.23.14/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig": Process exited with status 1
stdout:
stderr:
The connection to the server localhost:8443 was refused - did you specify the right host or port?
output: "\n** stderr ** \nThe connection to the server localhost:8443 was refused - did you specify the right host or port?\n\n** /stderr **"
❗ unable to fetch logs for: describe nodes
There is no
/var/lib/minikube
folder on my systemOperating System
macOS (Default)
Driver
Docker
The text was updated successfully, but these errors were encountered: