Open jrodonnell opened 2 years ago
@jrodonnell I'm working on the fix, and it's not as straightforward as I was expecting. For one thing, our development environment doesn't work for users whose names contain a single quote!
But looking at the code, I'm wondering if you can get it to work if you switch to the containerd
container engine? Different code paths, and I don't see the containerd
code path carrying about the current home directory.
And I see that k3s
won't come up for the same reason as docker.
Actual Behavior
Booting up Rancher Desktop for the first time, the WSL integration fails and K8s never comes up.
Steps to Reproduce
Result
UI shows this error:
wsl.log shows this:
And wsl-exec.log shows this:
Expected Behavior
Everything comes up and works!
Additional Information
Obvious workaround is to just change my account name, however this is happening on my work laptop and I do not have the permissions in my org to change my profile name ☹️ .
Rancher Desktop Version
1.2.1
Rancher Desktop K8s Version
1.22.7
Which container runtime are you using?
moby (docker cli)
What operating system are you using?
Windows
Operating System / Build Version
Windows 10 Pro 21H2
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
No response
Windows User Only
Microsoft Office profile is setting my local username so I can't change it.