This message was deleted.
# rancher-desktop
a
This message was deleted.
l
I also don't seem to have a
~/.kube/config
?
p
Your logs look like a normal-ish shut down (that is, it says it's shutting down stuff first, then stuff starts shutting down). Maybe there are more logs available? (Enabling debug mode will produce more verbose logs; that might be helpful.)
l
Copy code
2025-03-13T17:03:13.289Z: UnhandledRejectionWarning: Error: ENOENT: no such file or directory, watch '/Users/farida.sabry/.kube/config'
p
Hmm, do you have more context for that line? (Mostly because we should catch the error; we actually re-create the watcher later so it's harmless)
l
the rest in that log looks fine, but in diagnostics.log there's this
Copy code
2025-03-13T17:03:13.528Z: ERROR checking KUBE_CONTEXT {
  e: c [Error]: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/bin/kubectl exited with code 1
      at ChildProcess.<anonymous> (/Applications/Rancher Desktop.app/Contents/Resources/app.asar/dist/app/background.js:2:45866)
      at ChildProcess.emit (node:events:518:28)
      at ChildProcess._handle.onexit (node:internal/child_process:293:12) {
    command: [
      '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/bin/kubectl',
      'config',
      'view',
      '--minify',
      '--output=json'
    ],
    stdout: '',
    stderr: 'error: current-context must exist in order to minify\n',
    code: 1,
    [Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/bin/kubectl config view --minify --output=json'
  }
p
Ah,
diagnostics.log
basically is never useful for tracking down why things catastrophically broke. It's just extra checks to look for common issues (that wouldn't affect the app from running).
l
okay well where should I check? the main issues I'm seeing are that .kube/config doesn't exist, and I seem to have weird tcp issues. What else should I try?