Closed darkn3rd closed 3 years ago
@darkn3rd
depsite the error message, your cluster seems to be healthy
๐ Done! kubectl is now configured to use "minikube" by default
E1012 17:11:42.656583 101069 start.go:240] kubectl info: exec: exit status 1
that is an odd error message, do you mind checking if you have installed "kubectl"
and you mind sharing "minikube status" output ?
and also the output of this command ?
minikube kubectl -- get pods -A
/triage needs-information /kind support
also not sure if you implied, do you NOT get an error without the appromor disalble?
sudo systemctl stop apparmor && sudo systemctl disable apparmor
@medyagh When I run dmesg -w and run minikube start, I see apparmor deny messages for libvirt components. For this reason, I disabled it and restarted to rule out any issues with apparmor as a precaution.
Also for the requested command:
$ minikube kubectl -- get pods -A
> kubectl.sha256: 65 B / 65 B [--------------------------] 100.00% ? p/s 0s
> kubectl: 41.01 MiB / 41.01 MiB [--------------] 100.00% 138.66 MiB p/s 0s
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-f9fd979d6-kk6tn 1/1 Running 0 62s
kube-system etcd-minikube 0/1 Running 0 62s
kube-system kube-apiserver-minikube 1/1 Running 0 62s
kube-system kube-controller-manager-minikube 0/1 Running 0 62s
kube-system kube-proxy-gl2b7 1/1 Running 0 62s
kube-system kube-scheduler-minikube 0/1 Running 0 62s
kube-system storage-provisioner 1/1 Running 1 68s
I had some weird bizarre version of kubectl
, and have no idea how I got this one:
Client Version: version.Info{Major:"0", Minor:"10+", GitVersion:"v0.10.0-dirty", GitCommit:"71e26cbeb9c0bf1b6cc4c29b1f9d930e53513911", GitTreeState:"dirty"}
So I replaced it:
LATEST_KUBE=$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)
curl -sOL https://storage.googleapis.com/kubernetes-release/release/$LATEST_KUBE/bin/linux/amd64/kubectl
chmod +x ./kubectl
sudo mv ./kubectl /usr/local/bin/kubectl
kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:32:58Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
And now it seems I am no longer getting this error. I guess we can close this issue.
Steps to reproduce the issue:
sudo systemctl stop apparmor && sudo systemctl disable apparmor
E1012 17:04:57.003973 100058 start.go:240] kubectl info: exec: exit status 1
F1012 17:05:28.971138 100368 get.go:158] Get http://localhost:8080/api/v1beta1/pods?namespace=default: dial tcp 127.0.0.1:8080: connection refused
Full output of failed command:
Full output of
minikube start
command used, if not already included:(see above)
Optional: Full output of
minikube logs
command: