This message was deleted.
# rancher-desktop
a
This message was deleted.
q
Apparently the UX doesn't know that it can't let me choose 9p + vz
f
Thanks, I'll file a bug
q
i'm almost done filing
f
Even better 😄
Um, I'm not sure I can fix my config 😮
f
Why not?
q
I changed the settings and restarted and it was still broken...
hmm, changing both back to qemu seems to have worked
i had tried changing 9p to virtiofs
Yeah, something's wonky
ok, so, i start w/ qemu(sshfs) + qemu
if i change just the vm type to vz, i get the error about 9p
f
That sounds wrong. You switch from qemu/ssh to vz/ssh and get an error about 9p?
q
yep
f
Weird. I cannot reproduce this
q
My guess is that the original steps corrupted my config in some amusing manner...
f
idk, still not able to repro 🤷
I noticed that once I got into the vz/9p error state, RD would no longer restart the VM, even when I changed settings, I had to quit and restart
q
Yeah, I noticed that too, but restarting wasn't enough to unwedge me
i mean, i'm able to get back to sshfs/qemu, but it's still slightly corrupt afaict
f
You can check your
settings.json
and
lima.yaml
files to see if they have any traces of 9p in them
q
where do those hide?
f
Copy code
~/Library/Preferences/rancher-desktop/settings.json
q
yep
f
Copy code
~/Library/Application Support/rancher-desktop/lima/0/lima.yaml
q
oh
f
The files look fine to me. The
9p
options under the individual mounts are ignored unless
mountType
is set to
9p
.
q
is there an overrides file I need to check?
f
Could be, would be in
Copy code
~/Library/Application Support/rancher-desktop/lima/_config/override.yaml
I think; look around in the
_config
directory
There you go! You should delete the
mountType
and
mounts
part of the file now
q
ok, well, the gui will have to warn about this, but that's perhaps a separate ticket
f
We will not add any code checking
override.yaml
settings; that is
you break it, you keep all the pieces
territory, Same as any changes you make to the VM with
rdctl shell
.
q
kinda unfair
browsers have code when they change major versions to suggest discarding old prefs
f
What we do need to do is, is to expose all the settings in the UI so that
override.yaml
and modifying the VM becomes mostly unneccessary.
👍 1
q
i set that a long time ago before the vz stuff was added
f
I would agree that we should create a diagnostic to warn that the
override.yaml
file exists at all.
q
i'll leave that ticket to you 🙂 i don't understand the diagnostics well enough to characterize the ticket