This message was deleted.

seems like you had an earlier version of RD installed? you can always do a

wsl --unregister

of those old rancher-desktop and rancher-desktop-data distributions so that the new boostrap can replace them

I have similar problem with Rancher erroring out with

Error: Error registering WSL2 distribution

? I keep getting it every day, I've found the workaround (closing the Rancher, restarting WSL, opening up the Rancher), but as a result my images and pods are constantly deleted and I need to reinstall them again and again. I am on version 1.12.3 Logs:

2024-03-19T14:45:16.477Z: Check CONNECTED_TO_INTERNET result: {"description":"The application cannot reach the general internet for updated kubernetes versions and other components, but can still operate.","passed":true,"fixes":[]}
2024-03-19T14:45:21.467Z: Running check CONNECTED_TO_INTERNET
2024-03-19T14:45:21.482Z: Check CONNECTED_TO_INTERNET result: {"description":"The application cannot reach the general internet for updated kubernetes versions and other components, but can still operate.","passed":true,"fixes":[]}
2024-03-19T14:45:26.472Z: Running check CONNECTED_TO_INTERNET


2024-03-19T14:26:19.715Z: Updating release version cache with 178 items in cache
2024-03-19T14:26:21.501Z: updateCache: error: FetchError: request to <https://update.k3s.io/v1-release/channels> failed, reason: read ECONNRESET
2024-03-19T14:26:21.982Z: FetchError: request to <https://update.k3s.io/v1-release/channels> failed, reason: read ECONNRESET
2024-03-19T14:26:21.982Z: updateCache failed: FetchError: request to <https://update.k3s.io/v1-release/channels> failed, reason: read ECONNRESET
2024-03-19T14:26:37.363Z: Ensuring images available for K3s 1.27.6


2024-03-19T14:26:35.514Z: UnhandledRejectionWarning: FetchError: request to <https://desktop.version.rancher.io/v1/checkupgrade> failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\node-fetch\lib\index.js:1501:11)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}

Are you able to do a factory reset one time and retry?

I actually did that and it still showed me the same error. I downgraded to 12.2.2 and the problem seems to be resolved

are you able to share some of the logs with me?

most of developers in my company use 12.2.2 which is stable for them, and actually almost everyone's having issues with 12.2.3. I already downgraded and got my pods up, so if I get the same error with wsl again I will try 1.13.0. Thanks!

Are you behind a VPN?

yes

can you enable the network tunnel and try again?

if you talking about enabling it in rancher, it is enabled already

hmmm, from the logs you pasted it doen’t seem like it because I see:

2024-05-06T14:25:30.854Z: Running: wsl.exe --distribution rancher-desktop --exec busybox cp /mnt/c/Users/DSTELM~1/AppData/Local/Temp/rd-vtunnel-peer-ZNUE6w/vtunnel-peer /etc/init.d/vtunnel-peer

hmm, I can disable it and enable it again?

sure, it’s under wsl-> networking tab

Rancher was still Red after reenabling it, but fully closed and opened it and it seems fine. Bet it would still error out next time I restart my system though

are you able to do a factory reset, and then enable the network tunnel?

would factory reset remove all my pods and containers?

I think so, the only thing you will get to keep is cached kubernetes images 😐

okay, I will factory reset, and provide update if I get the same problem with wsl. Cannot restart my system for a while..

Sure, thanks

Hey Diana did everything work fine when you enabled the networking tunnel? I also get the same error : wsl.exe exited with code 4294967295 error.

Enabling tunnel didn’t do anything as it was already enabled. But resetting the whole rancher seemed like a temp solution, haven’t had an error in 2 day. Although was having trouble getting up Kafka container

Interesting ok. Yeh for me I just quit rancher desktop and restart the machine whenever I get this error (very inconvenient) I’ve disabled the k8s preference for now as we aren’t using it at the minute in our team , we’re using rancher desktop as an alternative to docker desktop. Not that it matters, random question, but what terminal are you using for your dev work while using rancher is it an Ubuntu terminal?

Windows cmd

I get this whenever I wanna use a Cmd terminal while using R-D :(

is rd in containerd or moby mode?

Moby

and RD is running? maybe

docker context ls

could point at the issue? and did you istall RD as admin? Is Rancher Desktop Privileged Service running?

Yes it’s running and installed rd using the winget install command on an elevated power shell terminal

so what contexts are listed?

What’s interesting is running docker context ls Ubuntu terminal vs cmd terminal one shows pipe that doesn’t work and the other is unix

well ubuntu will need the integration stuff configured so i would start w docker in the host and then move to another wsl distro

Yeh I’ve got it configured on rd side of things if that’s what you mean

yeah but if it doesn't work in host than it won't work in another distro that needs to hairpin through the host

Interesting, how do I go about doing that Justin?

does disagnostics show anything?

Let me have a look

did this machine use to have Docker Desktop on it?

Yes but wiped it

you could also try

[system.io.directory]::getaccesscontrol("\\.\pipe\docker-engine")

from a powershell terminal

Ok will try this and let you know how it goes thank you very much for your time

its a guess for the moment, but everything else seems fine

The machine is very restricted as it’s a work laptop May have to reach out to the higher powers

and as a note you can install and run RD as a User (not admin) and while there are a couple downsides I tend to recommend that context for locked down environments. makes life much easier if there are elevated rights gatekeepers

hey justin how can i get rancher in user mode? shall i delete the version of r-d ive got now if yes then how do i install the user mode version?

not all community recipes support --scope. if you try and install RD from a User cmd window (non-admin) it will prompt about asking for admin.

so non admin cmd window it is, i should try install via this?

you will need to uninstall the machine scoped RD first

cool will delete it

its something to try. something is preventing you from using that named pipe and you are the only one to be able to check that. running as a user may just have different results

getting the wsl error again and again..same logs, it keeps deleting my containers and images..

i would uninstall RD and then make sure all the distros are gone

wsl -l -v

and swing through %LOCALAPPDATA%\rancher-desktop as well to check for anything left over. Once you are sure there is nothing than try a reinstall. I am going to assume your Ubuntu distro is working fine so WSL should be good to go