Open IsaSih opened 1 year ago
I can confirm the issue. I don't get an error dialog; Rancher Desktop seems to quit, but I see the error in background.log
.
The problem is not that the cache directory doesn't exist, but that the mount isn't working.
I've not tested further, but I suspect that some combinations of 9p
mount options don't work/make sense, and we should reject them in validation. Needs a comprehensive set of tests to figure this out.
Actual Behavior
lima fails to start the application with a combination of experimental settings, as the following:
Steps to Reproduce
Result
Rancher Desktop fails to start Kubernetes because it looks for the cache directory that does not exist.
Last command run:
limactl shell --workdir=. 0 sudo bin/install-k3s v1.27.4+k3s1 /Users/isasih/Library/Caches/rancher-desktop/k3s
Fatal error:
Logs: Archive.zip Archive.zip
Expected Behavior
Rancher Desktop must successfully restart with a combination of any experimental settings that are within the range specified
Additional Information
No response
Rancher Desktop Version
1.9.1-668-gafe9a483
Rancher Desktop K8s Version
1.27.4
Which container engine are you using?
moby (docker cli)
What operating system are you using?
macOS
Operating System / Build Version
macOS Monterey
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
None
Windows User Only
No response