kind-night-86062
03/06/2024, 12:10 AMbrief-van-91960
03/06/2024, 1:14 PMacceptable-soccer-28720
03/06/2024, 1:26 PMAction 14:13:44: DetectWSL.
Action start 14:13:44: DetectWSL.
MSI (c) (90:C8) [14:13:44:710]: Creating MSIHANDLE (1) of type 790542 for thread 4040
MSI (c) (90:E8) [14:13:44:710]: Invoking remote custom action. DLL: C:\Users\MRZVAT~1\AppData\Local\Temp\MSI2B29.tmp, Entrypoint: IsWSLInstalled
MSI (c) (90:50) [14:13:44:713]: Cloaking enabled.
MSI (c) (90:50) [14:13:44:713]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (90:50) [14:13:44:713]: Connected to service for CA interface.
MSI (c) (90!E4) [14:13:44:823]: Creating MSIHANDLE (2) of type 790531 for thread 16612
time="2024-03-06T14:13:44+01:00" level=info msg="Checking if WSL is installed..."
MSI (c) (90!E4) [14:13:44:823]: Closing MSIHANDLE (2) of type 790531 for thread 16612
MSI (c) (90!E4) [14:13:44:823]: Creating MSIHANDLE (3) of type 790531 for thread 16612
time="2024-03-06T14:13:44+01:00" level=trace msg="Got 0 appx packages"
MSI (c) (90!E4) [14:13:44:824]: Closing MSIHANDLE (3) of type 790531 for thread 16612
MSI (c) (90!E4) [14:13:44:824]: Creating MSIHANDLE (4) of type 790531 for thread 16612
time="2024-03-06T14:13:44+01:00" level=trace msg="Failed to get WSL appx package, trying inbox versions..."
MSI (c) (90!E4) [14:13:44:824]: Closing MSIHANDLE (4) of type 790531 for thread 16612
MSI (c) (90!E4) [14:13:44:923]: Creating MSIHANDLE (5) of type 790531 for thread 16612
time="2024-03-06T14:13:44+01:00" level=trace msg="wsl.exe --status exited" error="invalid write result"
MSI (c) (90!E4) [14:13:44:923]: Closing MSIHANDLE (5) of type 790531 for thread 16612
MSI (c) (90!E4) [14:13:44:924]: Creating MSIHANDLE (6) of type 790531 for thread 16612
time="2024-03-06T14:13:44+01:00" level=error msg="Failed to get WSL info: invalid write result"
MSI (c) (90!E4) [14:13:44:924]: Closing MSIHANDLE (6) of type 790531 for thread 16612
CustomAction DetectWSL returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (90:E8) [14:13:44:925]: Closing MSIHANDLE (1) of type 790542 for thread 4040
Action ended 14:13:44: DetectWSL. Return value 3.
MSI (c) (90:C8) [14:13:44:926]: Doing action: FatalError
Action 14:13:44: FatalError.
Action start 14:13:44: FatalError.
Action 14:13:44: FatalError. Dialog created
MSI (c) (90:20) [14:13:44:941]: Note: 1: 2731 2: 0
Action ended 14:13:47: FatalError. Return value 2.
gentle-stone-75506
03/06/2024, 1:48 PMError: UNKNOWN: unknown error, open '\\wsl$\rancher-desktop-data\etc\hosts'
After digging in a little bit, I ran 'wsl -l -v' and saw that rancher-desktop-data is not present (I only see Ubuntu 22 and rancher-desktop).
Does anyone have any solution? I feel like I've already searched anywhere, none of my colleagues could even help me...
I'm pretty sure the problem is self-explanatory, but still - here's the background.log file:
2024-03-06T13:43:34.759Z: Failed to load kubeconfig, ignoring: TypeError: Cannot read properties of undefined (reading 'clusters')
at KubeConfig.loadFromString (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\@kubernetes\client-node\dist\config.js:115:61)
at KubeConfig.loadFromFile (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\@kubernetes\client-node\dist\config.js:76:14)
at KubeConfig.loadFromDefault (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\@kubernetes\client-node\dist\config.js:249:22)
at Zs.updateContexts (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:112261)
at new Zs (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:108034)
at Zs.getInstance (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:109697)
at C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:146895
at async C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:146410
2024-03-06T13:43:34.766Z: Failed to load kubeconfig, ignoring: TypeError: Cannot read properties of undefined (reading 'clusters')
at KubeConfig.loadFromString (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\@kubernetes\client-node\dist\config.js:115:61)
at KubeConfig.loadFromFile (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\@kubernetes\client-node\dist\config.js:76:14)
at KubeConfig.loadFromDefault (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\@kubernetes\client-node\dist\config.js:249:22)
at Zs.updateContexts (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:112261)
at Zs.buildFromConfig (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:110321)
at new Zs (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:108257)
at Zs.getInstance (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:109697)
at C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:146895
at async C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:41:146410
2024-03-06T13:43:35.164Z: Stopping background process Win32 socket proxy (pid <none>).
2024-03-06T13:43:54.147Z: mainEvents settings-update: {"version":10,"application":{"adminAccess":false,"debug":false,"extensions":{"allowed":{"enabled":false,"list":[]},"installed":{}},"pathManagementStrategy":"manual","telemetry":{"enabled":true},"updater":{"enabled":true},"autoStart":false,"startInBackground":false,"hideNotificationIcon":false,"window":{"quitOnClose":false}},"containerEngine":{"allowedImages":{"enabled":false,"patterns":[]},"name":"moby"},"virtualMachine":{"memoryInGB":2,"numberCPUs":2,"hostResolver":true},"WSL":{"integrations":{}},"kubernetes":{"version":"1.28.7","port":6443,"enabled":false,"options":{"traefik":true,"flannel":true},"ingress":{"localhostOnly":false}},"portForwarding":{"includeKubernetesServices":false},"images":{"showAll":true,"namespace":"k8s.io"},"containers":{"showAll":true,"namespace":"default"},"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":true,"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"]}}}}
2024-03-06T13:43:54.324Z: Stopping background process Win32 socket proxy (pid <none>).
2024-03-06T13:43:54.612Z: Stopping background process Win32 socket proxy (pid <none>).
2024-03-06T13:44:01.288Z: Launching background process Win32 socket proxy.
2024-03-06T13:44:33.043Z: Background process Win32 socket proxy (pid 21536) exited with status 1 signal null
2024-03-06T13:44:34.049Z: Launching background process Win32 socket proxy.
2024-03-06T13:44:40.272Z: Kubernetes was unable to start: [Error: UNKNOWN: unknown error, open '\\wsl$\rancher-desktop-data\etc\hosts'] {
errno: -4094,
code: 'UNKNOWN',
syscall: 'open',
path: '\\\\wsl$\\rancher-desktop-data\\etc\\hosts'
}
2024-03-06T13:44:40.273Z: Stopping background process Win32 socket proxy (pid 16680).
2024-03-06T13:44:40.517Z: Background process Win32 socket proxy (pid 16680) exited gracefully.
TIA :)gentle-stone-75506
03/06/2024, 1:48 PMgentle-stone-75506
03/06/2024, 1:51 PMgentle-stone-75506
03/06/2024, 2:09 PMsteep-window-51379
03/06/2024, 2:17 PMfast-garage-66093
03/07/2024, 2:02 AMvirtiofs
mount type. In our testing for the upcoming 1.13.0 release we have experienced catastrophic data loss with this mount option on Linux (the $HOME
directory on the host was wiped clean). There has been a single report against Lima from a user experiencing the same on macOS using VZ with virtiofs
. Please use the default (and non-experimental) reverse-sshfs
exclusively for now!
We will be temporarily removing the virtiofs
option in the 1.13.0 release until the problem is understood and fixed.
I've been personally using VZ and virtiofs
on an M1 macOS system without problems for quite a while, and run the full Rancher Desktop integration test suite with that configuration too. But since the failure mode is so catastrophic I want to urge everyone not to use this setting for now!gentle-stone-75506
03/07/2024, 7:28 AMquick-keyboard-83126
03/07/2024, 3:30 PMaverage-minister-67800
03/08/2024, 11:39 PMbored-farmer-36655
03/09/2024, 1:18 AMfast-garage-66093
03/09/2024, 1:31 AM/home/*
into the VM, which doesn't happen on macOS (it is called /Users
on macOS, so won't conflict with /home
inside the VM).
I suspect nobody ran into this so far because virtiofs
doesn't actually work on Linux unless you install the Rust implementation of virtiofsd
on the host, which most people probably don't do. Which in this case is a good thing...bored-farmer-36655
03/09/2024, 7:12 PMzypper rm virtiofsd
The following 7 packages are going to be REMOVED:
libguestfs libguestfs-appliance libguestfs-winsupport libguestfs-xfs perl-Sys-Guestfs qemu-tools virtiofsd
zypper in qemu-tools
The following package is recommended, but will not be installed due to conflicts or dependency issues:
multipath-tools
The following 2 NEW packages are going to be installed:
qemu-tools virtiofsd
quick-dentist-56265
03/12/2024, 9:13 AMquick-dentist-56265
03/12/2024, 9:14 AMdocker-credentials-wincred
get call freezes, preventing the tool to function correctly.
Has anyone had a similar issue?quick-dentist-56265
03/12/2024, 9:15 AMquick-dentist-56265
03/12/2024, 12:43 PMfast-garage-66093
03/13/2024, 8:49 PMlimited-pizza-33551
03/14/2024, 2:22 AMcool-school-99182
03/14/2024, 12:07 PMbored-farmer-36655
03/14/2024, 12:22 PMcool-school-99182
03/14/2024, 12:22 PMbored-farmer-36655
03/14/2024, 12:23 PMbulky-potato-22114
03/18/2024, 1:08 PMbulky-potato-22114
03/18/2024, 1:08 PM2024-03-18T09:30:40.391Z: Registered distributions: Ubuntu,rancher-desktop,rancher-desktop-data
2024-03-18T09:30:40.969Z: Registered distributions:
2024-03-18T09:30:41.281Z: WSL failed to execute wsl.exe --import rancher-desktop C:\Users\user.Name\AppData\Local\rancher-desktop\distro C:\Program Files\Rancher Desktop\resources\resources\win32\distro-0.55.tar --version 2: Error: wsl.exe exited with code 4294967295
executing the command my self gives:
Import in progress, this may take a few minutes.
A distribution with the supplied name already exists.
Error code: Wsl/Service/0x800700b7
but i noticed that the command requires " around the tar filename... cause it has space in the path namebulky-potato-22114
03/18/2024, 1:09 PMlittle-horse-77834
03/18/2024, 4:21 PMproud-jewelry-46860
03/18/2024, 4:58 PM