https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
c
Your error could be similar to #2728. Are you running behind a corporate proxy or VPN?
h
I have tried with both VPN enabled and disabled but Rancher desktop still reports The application cannot reach the general internet for updated kubernetes versions and other components, but can still operate. I would appreciate any pointers on how to debug. I have not had any issue with other apps using Cisco Any Connect which is the VPN software I use to connect to NVidia and for general protection.
Does Rancher Desktop generate any log files that could help with identifying what the issue is. If I launch Rancher Desktop within Powershell I get no output. If I run it inside WSL I get the error mwoodpatrick@westie-k0s:/mnt/c/Program Files/Rancher Desktop$ './Rancher Desktop.exe' --trace-warnings (node:43884) UnhandledPromiseRejectionWarning: Error: C:\WINDOWS\system32\wsl.exe exited with code 4294967295 at ChildProcess.<anonymous> (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js17721) at ChildProcess.emit (nodeevents390:28) at Process.ChildProcess._handle.onexit (nodeinternal/child process290:12) (Use 
Rancher Desktop --trace-warnings ...
to show where the warning was created) (node:43884) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag 
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
c
Rancher Desktop logs are generated under 
%USERPROFILE%\AppData\Local\rancher-desktop\logs
in Windows. The first place I would look is 
background
log. It might be beneficial to enable debug logging (found under Troubleshooting => Logs or via 
rdctl set --application.debug=true
)
In the absence of additional logs, I'm curious if this issue could be related to what you're experiencing https://github.com/rancher-sandbox/rancher-desktop/issues/1807
h
looking at background.log it shows an error when starting wsl its trying to open a distro which does not exist and not the default disto. I'm curious as to where its getting this disto name from
w
which distro was having an error? was virtualmachineplatform and WSL OS parts and WSL windows store parts installed before trying RD? I have had mixed results installing RD or other WSL2 users where the features were not in place and functional before. An reinstalling doesn’t seem to do the registration step so I have manually deleted the distro folders after uninstalling so they get recreated and registered during the next install
h
WSL-2 was installed long before I tried using Rancher desktop and have multiple projects running on multiple distros without issue. Deleting existing distro's is not really workable for me. I'm trying to use Rancher Desktop to manage containers not to install WSL distros
w
yeah RD uses WSL2 for its Linux environment. I meant you may need to delete the rancher-desktop and rancher-desktop-data distros manually after an uninstall
h
Is there documentation on how the rancher-desktop and rancher-desktop-data distros are generated somewhere I would like to add rancher-desktop to one of my other distros. I tried adding it to one of my distros but when I run it I get: rancher-desktop libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [8049270228/055339.759383ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. [8049270228/055339.770539ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
w
well the distro is a vhdx including the alpine userspace so taking out the parts of the above userspace for a custom distro I think will be interesting to say the least
h
But I assume there should be docs somewhere on how the vhdx was created
f
I don't know what you mean by "add to my other distros". The distro is generated by 
wsl --import
from a tarball from one of the releases on Releases · rancher-sandbox/rancher-desktop-wsl-distro. But then it is further modified by Rancher Desktop as it starts up. You should not really interact with it directly; not sure what you are trying to do.
I suspect your original problem is similar to Rancher Desktop V 1.7.0 fails to start on Windows 11 · Issue #3785
h
I have a custom distro that I'm building which is based on Ubuntu and includes k3s I would like to be able to launch rancher from that distro not be required to run a second distro in order to have access to rancher
f
Not sure if you mean "Rancher Desktop" or "Rancher Manager". The former is using a custom 
rancher-desktop
distro as part of the implementation, and that part cannot be replaced. You can install the latter into your own cluster using e.g. 
helm install
.
h
Understood I was wanting to review what the steps were to build rancher desktop since I would like to adapt that flow to fit within our other constraints and goals.
f
The RD distro is based on Alpine and uses OpenRC instead of systemd. If you are already managing your own k3s on Ubuntu, I don't know what parts of the distro would be useful to you.
h
I'm not sure either that's why I wanted to understand the rancher desktop build process better. It may be doing some things in a better way than we are currently
f
I gave you the link to the repo for the distro above. Everything else is configured at runtime via the Electron app. You will have to look at the source code to see what it does. Everything in Rancher Desktop is open source.
h
Thanks for the info, I will review
475 Views
Open in Slack
PreviousNext
Powered by