https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Take a look at the logs under 
~/Library/Logs/rancher-desktop/
to see if they have any additional details. Maybe start with 
background.log
if the app fails by itself before showing the UI
f
Copy code
2023-11-06T20:12:54.915Z: Error starting up: Error: Invalid strategy "undefined" Error: Invalid strategy "undefined"
    at os (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:73078|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:73078>)
    at /Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:143171|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:143171>
Copy code
2023-11-06T20:12:52.799Z: Error reading cached version data, discarding: [Error: ENOENT: no such file or directory, open '/Users/samir/Library/Caches/rancher-desktop/k3s-versions.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/samir/Library/Caches/rancher-desktop/k3s-versions.json'
}
2023-11-06T20:12:54.908Z: Error reading cached version data, discarding: [Error: ENOENT: no such file or directory, open '/Users/samir/Library/Caches/rancher-desktop/k3s-versions.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/samir/Library/Caches/rancher-desktop/k3s-versions.json'
}
2023-11-06T20:12:54.908Z: Updating release version cache with 0 items in cache
Copy code
2023-11-06T20:12:54.903Z: Error JSON-parsing existing settings contents {"version":4,"application":{"adminAccess":true,"debug":false,"telemetry":{"enabled":true},"updater":{"enabled":true}},"containerEngine":{"allowedImages":{"enabled":false,"patterns":[]},"name":"moby"},"virtualMachine":{"memoryInGB":10,"numberCPUs":4},"WSL":{"integrations":{}},"kubernetes":{"version":"v1.19.9","port":6443,"enabled":true,"options":{"traefik":true,"flannel":true},"ingress":{"localhostOnly":false},"memoryInGB":10,"numberCPUs":4,"containerEngine":"moby","checkForExistingKimBuilder":false},"portForwarding":{"includeKubernetesServices":false},"images":{"showAll":true,"namespace":"<http://k8s.io|k8s.io>"},"diagnostics":{"showMuted":false,"mutedChecks":{}},"experimental":{"virtualMachine":{"type":"qemu","useRosetta":false,"socketVMNet":false,"mount":{"type":"reverse-sshfs","9p":{"securityModel":"none","protocolVersion":"9p2000.L","msizeInKib":128,"cacheMode":"mmap"}},"networkingTunnel":false,"proxy":{"enabled":false,"address":"","password":"","port":3128,"username":"","noproxy":["0.0.0.0/8","10.0.0.0/8","127.0.0.0/8","169.254.0.0/16","172.16.0.0/12","192.168.0.0/16","224.0.0.0/4","240.0.0.0/4"]}}},"telemetry":true,"updater":true,"debug":false} TypeError: Cannot read properties of undefined (reading 'socketVMNet')
    at 4 (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:45950|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:45950>)
    at /Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:43206|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:43206>
    at /Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:43637|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:43637>
    at D (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:43801|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:29:43801>)
    at /Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:140684|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:140684>
2023-11-06T20:12:54.904Z: The old settings file will be replaced with the default settings.
2023-11-06T20:12:54.904Z: appVersion is 1.11.0
f
Oh, this means you had a very old version of Rancher Desktop installed before. Assuming you don't care about the content of the old VM, the easiest way to fix it would be to run 
rdctl factory-reset
You have to specify the full path to 
rdctl
because it probably hasn't been configured yet
Once you do this, the app should start properly
f
yeah I was an early adopted I think was running the earliest beta or such when dockerd was JUST introduced
f
You could also try to run 
rm ~/Library/Preferences/rancher-desktop/settings.json
That should be enough to unblock, but you should still consider doing a factory-reset later then
f
No such file on the rm
Copy code
./Resources/resources/darwin/bin/rdctl factory-reset                                                                                                                (docker-desktop/default)
WARN[0000] Non-strict YAML is deprecated and will be unsupported in a future version of Lima  comment="main file \"/Users/samir/Library/Application Support/rancher-desktop/lima/0/lima.yaml\"" error="[111:1] unknown field \"k3s\"\n      108 |     writable: true\n      109 |   - location: /tmp/rancher-desktop\n      110 |     writable: true\n    > 111 | k3s:\n            ^\n      112 |   version: 1.19.9\n      113 | networks:\n      114 |   - lima: rancher-desktop-shared\n      115 |     "
INFO[0000] The qemu driver process seems already stopped
INFO[0000] The host agent process seems already stopped
INFO[0000] Removing /Users/samir/Library/Application Support/rancher-desktop/lima/0 under "*.pid *.sock *.tmp"
WARN[0000] Non-strict YAML is deprecated and will be unsupported in a future version of Lima  comment="main file \"/Users/samir/Library/Application Support/rancher-desktop/lima/0/lima.yaml\"" error="[111:1] unknown field \"k3s\"\n      108 |     writable: true\n      109 |   - location: /tmp/rancher-desktop\n      110 |     writable: true\n    > 111 | k3s:\n            ^\n      112 |   version: 1.19.9\n      113 | networks:\n      114 |   - lima: rancher-desktop-shared\n      115 |     "
INFO[0000] Deleted "0" ("/Users/samir/Library/Application Support/rancher-desktop/lima/0")
No matching processes belonging to you were found
f
Did you already do the factory reset? That would also have deleted the file already
f
trying it out now.. we’ll see if this works and yes I did the reset
f
Ok, now try to run the app again
You should now get the "first-run" dialog
f
looks better so far
2 Views
Open in Slack
PreviousNext
Powered by