https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Any errors in 
background.log
?
q
full macos path?
f
Copy code
cat ~/Library/Logs/rancher-desktop/background.log
q
Copy code
2023-12-14T18:38:19.714Z: Still processing the first-run dialog: not opening main window
2023-12-14T18:38:24.831Z: Error starting up: Error: Invalid strategy "notset" Error: Invalid strategy "notset"
    at ss (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:73148|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:73148>)
    at /Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:143253|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:143253>
f
That one is benign (there can be up to 3 of them). Anything later in the file?
q
EOF
f
Oh, wait, it says 
notset
. What version did you upgrade from?
q
i think the 
.0
version?
but i can't really ask it any questions right now
f
It now depends on how much of your current settings you want/need to preserve: 1. factory-reset should fix this 2. deleting just 
settings.json
should fix it, but resets your config (but not the VM) 3. you could edit 
settings.json
and change 
notset
to 
rcFiles
You need to quit Rancher Desktop before doing 2 or 3
q
Copy code
% ps aux|grep -i rancher
jsoref           72356   0.0  0.0 408626896   1408 s060  S+    1:50PM   0:00.00 grep -i rancher
i don't think it's open?
f
Copy code
~/Library/Preferences/rancher-desktop/settings.json
Wait, try this:
q
Copy code
{
  "version": 4,
  "application": {
    "adminAccess": true,
    "debug": false,
    "pathManagementStrategy": "notset",
    "telemetry": {
      "enabled": true
    },
    "updater": {
      "enabled": true
    }
  },
  "containerEngine": {
    "allowedImages": {
      "enabled": false,
      "patterns": [],
      "locked": false
    },
    "name": "moby"
  },
  "virtualMachine": {
    "memoryInGB": 2,
    "numberCPUs": 2
  },
  "WSL": {
    "integrations": {}
  },
  "kubernetes": {
    "version": "1.27.5",
    "port": 6443,
    "enabled": false,
    "options": {
      "traefik": true,
      "flannel": true
    },
    "ingress": {
      "localhostOnly": false
    },
    "memoryInGB": 2,
    "numberCPUs": 2,
    "containerEngine": "containerd",
    "checkForExistingKimBuilder": false,
    "WSLIntegrations": {},
    "suppressSudo": false,
    "experimentalHostResolver": false
  },
  "portForwarding": {
    "includeKubernetesServices": false
  },
  "images": {
    "showAll": true,
    "namespace": "buildkit"
  },
  "diagnostics": {
    "showMuted": true,
    "mutedChecks": {
      "KUBE_CONTEXT": true
    }
  },
  "experimental": {
    "virtualMachine": {
      "type": "vz",
      "useRosetta": true,
      "socketVMNet": false,
      "mount": {
        "type": "virtiofs",
        "9p": {
          "securityModel": "none",
          "protocolVersion": "9p2000.L",
          "msizeInKib": 128,
          "cacheMode": "mmap",
          "msizeInKB": 128
        }
      },
      "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,
  "pathManagementStrategy": "notset"
}
f
Copy code
rdctl start --application.path-management-strategy rcfiles
q
rancher!
Version: 1.11.1 Check for updates automatically
f
If that doesn't work, try editing the 
settings.json
and change 
notset
to 
rcfiles
q
no, that seemed to work
well, progress, anyway
f
Not sure how this can happen; it normally means that you are just upgrading from 
1.2.1
or so
q
i was not! I was almost certainly on 1.11.0
f
Somehow your settings file got corrupted. Move it away, start again, and then setup the settings based on your current file
"version":4
is ancient, so somehow you got a very old settings file; maybe restored from backup or something? It should be version `10`if you upgraded from 1.11.0
q
i don't think i've ever done a restore
i have limped along w/ upgrades usually single versions not large jumps
oh
there was a small time when i was testing self builds
f
I just wonder if the VM is in a similarly ancient state, and you would be better off with an 
rdctl factory-reset
Sorry, meetings now...
q
i'll do a factory-reset
4 Views
Open in Slack
PreviousNext
Powered by