This message was deleted.
# rancher-desktop
a
This message was deleted.
b
more logs : Error Starting Kubernetes
Copy code
TypeError: Cannot read properties of undefined (reading 'clusters')
Context: Installing trivy & CA certs Some recent logfile lines:
Copy code
at KubeConfig.loadFromFile (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/node_modules/@kubernetes/client-node/dist/config.js:77:14|Desktop.app/Contents/Resources/app.asar/node_modules/@kubernetes/client-node/dist/config.js:77:14>)
    at KubeConfig.loadFromDefault (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/node_modules/@kubernetes/client-node/dist/config.js:237:22|Desktop.app/Contents/Resources/app.asar/node_modules/@kubernetes/client-node/dist/config.js:237:22>)
    at bi.updateContexts (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:54882|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:54882>)
    at bi.updateMenu (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:53860|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:53860>)
    at bi.k8sStateChanged (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:53288|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:53288>)
    at g.<anonymous> (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:52540|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:52540>)
    at g.emit (node:events:402:35)
    at Br.<anonymous> (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:79560|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:79560>)
    at Br.emit (node:events:390:28)
I tried factory rest, but problem again.
I have uninstall docker before install.
I have uncheck the k8s option, why does it always start k8s at startup.
I tried recheck the k8s to install k3s, then disable k8s again, the error is disappeared. I don’t know why .
w
try resetting kubectl config - I had a similar issue and it turned out to be bad config in kubectl
(stuff in the
~/.kube/
directory)
b
You are right. I tried again according to your suggesting, it starts up normally.
👍 1
121 Views