Error Starting Rancher-desktop on Win10 with wsl error

[sunc2000]

Actual Behavior

Starting Rancher-desktop 1.3.0 . The software hangs up at the step waiting for nodes, and then it pops up a message box with the following error: Error Starting Kubernetes
Error:socket hang up

Context: Waiting for nodes

Some recent logfile lines: 2022-05-23T07:04:33.041Z: Registered distributions: rancher-desktop,rancher-desktop-data,Ubuntu-20.04 2022-05-23T07:04:33.540Z: Registered distributions: rancher-desktop,rancher-desktop-data,Ubuntu-20.04 2022-05-23T07:04:38.566Z: Registered distributions: rancher-desktop,rancher-desktop-data,Ubuntu-20.04 2022-05-23T07:04:38.970Z: Registered distributions: rancher-desktop,rancher-desktop-data,Ubuntu-20.04 2022-05-23T07:04:38.970Z: data distro already registered 2022-05-23T07:04:44.140Z: Stopping background process host-resolver vsock host. 2022-05-23T07:04:45.302Z: Did not find a valid mount, mounting /mnt/wsl/rancher-desktop/run/data 2022-05-23T07:04:52.027Z: Installing C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Users/xxx/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ... 2022-05-23T07:05:40.146Z: Launching background process Win32 socket proxy. 2022-05-23T07:05:41.062Z: WSL: executing: readlink -f $HOME/.docker/cli-plugins/docker-compose: Error: wsl.exe exited with code 1 2022-05-23T07:05:41.062Z: Failed to readlink/rm $HOME/.docker/cli-plugins/docker-compose Error: wsl.exe exited with code 1 at ChildProcess. (C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:17:141690) at ChildProcess.emit (node:events:390:28) at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) { stdout: '' }

Steps to Reproduce

just startup rancher-desktop software.

Result

Some recent logfile lines: 2022-05-23T07:04:33.041Z: Registered distributions: rancher-desktop,rancher-desktop-data,Ubuntu-20.04 2022-05-23T07:04:33.540Z: Registered distributions: rancher-desktop,rancher-desktop-data,Ubuntu-20.04 2022-05-23T07:04:38.566Z: Registered distributions: rancher-desktop,rancher-desktop-data,Ubuntu-20.04 2022-05-23T07:04:38.970Z: Registered distributions: rancher-desktop,rancher-desktop-data,Ubuntu-20.04 2022-05-23T07:04:38.970Z: data distro already registered 2022-05-23T07:04:44.140Z: Stopping background process host-resolver vsock host. 2022-05-23T07:04:45.302Z: Did not find a valid mount, mounting /mnt/wsl/rancher-desktop/run/data 2022-05-23T07:04:52.027Z: Installing C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Users/xxx/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ... 2022-05-23T07:05:40.146Z: Launching background process Win32 socket proxy. 2022-05-23T07:05:41.062Z: WSL: executing: readlink -f $HOME/.docker/cli-plugins/docker-compose: Error: wsl.exe exited with code 1 2022-05-23T07:05:41.062Z: Failed to readlink/rm $HOME/.docker/cli-plugins/docker-compose Error: wsl.exe exited with code 1 at ChildProcess. (C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:17:141690) at ChildProcess.emit (node:events:390:28) at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) { stdout: '' }

Expected Behavior

Kubernetes starts up

Additional Information

No response

Rancher Desktop Version

1.3.0

Rancher Desktop K8s Version

1.18.20

Which container runtime are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Win10 professional 19042.1706 20H2

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

No response

Windows User Only

No response

[rak-phillip]

This sounds potentially related to #2135 & #1772.

@sunc2000 do you happen to be on a corporate VPN? Would you be able to attach the contents of background.log to this issue so we can take a closer look? You can easily find its location by opening Rancher Desktop and navigating to Troubleshooting => Logs => Show Logs

[sunc2000]

I start the rancher-desktop again on my notebook in office and the vpn client offline. This time, it's a similar error during waiting for nodes:

1. background.log contents:

2022-05-23T23:37:12.206Z: event settings-read in main: [object Object] 2022-05-23T23:44:05.416Z: Kubernetes was unable to start: Error: Client network socket disconnected before secure TLS connection was established at connResetException (node:internal/errors:691:14) at TLSSocket.onConnectEnd (node:_tls_wrap:1585:19) at TLSSocket.emit (node:events:402:35) at endReadableNT (node:internal/streams/readable:1343:12) at processTicksAndRejections (node:internal/process/task_queues:83:21) { code: 'ECONNRESET', path: null, host: '172.25.213.172', port: '6443', localAddress: undefined

2. wsl.log contents：

2022-05-23T23:42:51.119Z: Capturing output: wsl.exe --list --quiet 2022-05-23T23:42:52.948Z: Capturing output: wsl.exe --list --verbose 2022-05-23T23:42:54.285Z: Capturing output: wsl.exe --distribution Ubuntu-20.04 --exec wslpath -a -u C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\wsl-helper 2022-05-23T23:42:57.879Z: Capturing output: wsl.exe --distribution Ubuntu-20.04 --exec /mnt/c/Users/xxx/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/wsl-helper kubeconfig --show 2022-05-23T23:43:00.998Z: Launching background process Win32 socket proxy. 2022-05-23T23:43:01.001Z: Capturing output: wsl.exe --distribution Ubuntu-20.04 --exec wslpath -a -u C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\bin\docker-compose 2022-05-23T23:43:03.063Z: Capturing output: wsl.exe --distribution Ubuntu-20.04 --exec readlink -f $HOME/.docker/cli-plugins/docker-compose 2022-05-23T23:43:05.333Z: WSL: executing: readlink -f $HOME/.docker/cli-plugins/docker-compose: Error: wsl.exe exited with code 1 2022-05-23T23:43:05.333Z: Failed to readlink/rm $HOME/.docker/cli-plugins/docker-compose Error: wsl.exe exited with code 1 at ChildProcess. (C:\Users\xxx\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:17:141690) at ChildProcess.emit (node:events:390:28) at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) { stdout: '' }

3. k3s.log contents:

E0523 23:44:02.908132 744 kubelet.go:2292] node "xxx_note" not found time="2022-05-23T23:44:02.945507200Z" level=info msg="waiting for node xxx_note: nodes "xxx_note" not found" E0523 23:44:03.009000 744 kubelet.go:2292] node "xxx_note" not found time="2022-05-23T23:44:03.034309600Z" level=info msg="Waiting for master node xxx_note startup: nodes "xxx_note" not found" E0523 23:44:03.109814 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:03.210798 744 kubelet.go:2292] node "xxx_note" not found I0523 23:44:03.212821 744 kubelet_node_status.go:294] Setting node annotation to enable volume controller attach/detach I0523 23:44:03.267763 744 kubelet_node_status.go:70] Attempting to register node xxx_note E0523 23:44:03.272540 744 kubelet_node_status.go:92] Unable to register node "xxx_note" with API server: Node "xxx_note" is invalid: metadata.name: Invalid value: "xxx_note": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*') E0523 23:44:03.311778 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:03.412603 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:03.513760 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:03.616124 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:03.718181 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:03.819816 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:03.904735 744 controller.go:228] failed to get node "xxx_note" when trying to set owner ref to the node lease: nodes "xxx_note" not found E0523 23:44:03.920546 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:04.021361 744 kubelet.go:2292] node "xxx_note" not found time="2022-05-23T23:44:04.057538200Z" level=info msg="Waiting for master node xxx_note startup: nodes "xxx_note" not found" E0523 23:44:04.122754 744 kubelet.go:2292] node "xxx_note" not found E0523 23:44:04.204590 744 csi_plugin.go:289] Failed to initialize CSINode: error updating CSINode annotation: timed out waiting for the condition; caused by: nodes "xxx_note" not found F0523 23:44:04.205130 744 csi_plugin.go:303] Failed to initialize CSINode after retrying: timed out waiting for the condition time="2022-05-23T23:44:11.634118500Z" level=info msg="Starting k3s v1.18.20+k3s1 (57b73dc9)" time="2022-05-23T23:44:11.635899800Z" level=info msg="Cluster bootstrap already complete" time="2022-05-23T23:44:11.675753200Z" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s" time="2022-05-23T23:44:11.676832800Z" level=info msg="Configuring database table schema and indexes, this may take a moment..." time="2022-05-23T23:44:11.678044500Z" level=info msg="Database tables and indexes are up to date" time="2022-05-23T23:44:11.695771900Z" level=info msg="Kine listening on unix://kine.sock" time="2022-05-23T23:44:11.699986200Z" level=info msg="Running kube-apiserver --advertise-port=6443 --allow-privileged=true --anonymous-auth=false --api-audiences=unknown --authorization-mode=Node,RBAC --basic-auth-file=/var/lib/rancher/k3s/server/cred/passwd --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/k3s/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction --etcd-servers=unix://kine.sock --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/k3s/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.key --proxy-client-cert-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/k3s/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6444 --service-account-issuer=k3s --service-account-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key" Flag --basic-auth-file has been deprecated, Basic authentication mode is deprecated and will be removed in a future release. It is not recommended for production environments. I0523 23:44:11.703762 1788 server.go:645] external host was not specified, using 172.25.213.172 I0523 23:44:11.705079 1788 server.go:162] Version: v1.18.20+k3s1

And I test the kubernetes master 172.25.213.172 with "kubectl cluster-info" command. The first time it failed with error: the server is currently unable to handle the request

But I try it again and it's ok. Kubernetes master is running at https://172.25.213.172:6443 CoreDNS is running at https://172.25.213.172:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy Metrics-server is running at https://172.25.213.172:6443/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy

And I test with "kubectl get pods -A", it's ok too. PS C:\WINDOWS\system32> kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system helm-install-traefik-x2b62 0/1 Pending 0 24h kube-system coredns-7944c66d8d-vjc7j 0/1 Pending 0 24h kube-system metrics-server-7566d596c8-zdtr6 0/1 Pending 0 24h kube-system local-path-provisioner-6d59f47c7-hd4c8 0/1 Pending 0 24h default nginx-f89759699-rszvq 0/1 Pending 0 21h

Three different errors? First, Some clinet connects to 172.25.213.172 failed (2022-05-23T23:44:05.416Z in background.log)before k3s server start up (23:44:11.705079 in k3s.log).

Second, wsl command failed to readlink docker-compose in distribution Ubuntu-20.04. Why does rancher-desktop use another distribution?

Third, in k3s.log there are many error info about "failed to get node "xxx_note" when trying to set owner ref to the node lease: nodes "xxx_note" not found" and "Failed to initialize CSINode: error updating CSINode annotation: timed out waiting for the condition; caused by: nodes "xxx_note" not found"

[yevon]

Exaclty same error here, just uninstalled Docker Desktop and installed Rancher Desktop 1.3.0 with this error. Windows 11 + wsl + Ubuntu integration. Tried changing container runtime to dockerd just in case but it doesen't work either.

[yevon]

Found: It was the hostname, it cannot contain any dash. After changing hostname-example to hostnameexample and restarting the pc, it worked.

[Oleg3n]

@yevon thank you!

[giggio]

Oops, same problem here, hostname has a dash. I can change the hostname, but it would go against company policy. Any workaround?

[jandubois]

I cannot reproduce this; I have a hostname of DESKTOP-4992680 and things work fine. Are you sure you don't have an underscore instead of a dash in your hostname?

[jandubois]

Are you sure you don't have an underscore instead of a dash in your hostname?

I can't even rename the computer to use an underscore in the name

[sunc2000]

My hostname is xxxx_note.

[sunc2000]

OS: win10 professional 21H2 19044.1766

[giggio]

I cannot reproduce this; I have a hostname of DESKTOP-4992680 and things work fine. Are you sure you don't have an underscore instead of a dash in your hostname?

No, it has a dash, not an underscore. I got the same error... It might be a coincidence, then.

[yevon]

Can somebody check isf upper-case or lower might affect? In my case it solved the problem instantly after trying everything

[darren-bell-optiva]

I havent been able to test it. But I'm wondering if it is related to having a "." (period) in my user name e.g. user.name instead of just "username"

[trevormduncan]

My error:

Kubernetes Error
Rancher Desktop 1.6.0 - win32 (x64)
Error Starting Kubernetes
Error: UNKNOWN: unknown error, open '\\wsl$\rancher-desktop-data\etc\hosts'
Context:
Updating /etc/hosts

Some recent logfile lines:
2022-10-15T12:09:53.042Z: Error registering data distribution: Error: tar.exe exited with code 128
2022-10-15T12:09:53.072Z: WSL failed to execute wsl.exe --unregister rancher-desktop-data: Error: wsl.exe exited with code 4294967295
2022-10-15T12:09:53.073Z: Error setting up data distribution: Error: wsl.exe exited with code 4294967295
    at ChildProcess.<anonymous> (C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:1:7750)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  code: 4294967295,
  command: [ 'wsl.exe', '--unregister', 'rancher-desktop-data' ]
}

It may not be the same, but I couldn't use Rancher Desktop from a fresh install. For some reason, it's not creating the rancher-desktop-data distro, and I can't get a log output as to why. However, if you manually create these two distros, it will work!

1. Factory reset Rancher Desktop & Shutdown WSL

wsl --shutdown

2. Create the rancher-desktop distro

C:\Users\anon>wsl.exe --import rancher-desktop C:\Users\anon\AppData\Local\rancher-desktop\rancher-desktop "C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\distro-0.27.tar" --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

3. Create the rancher-desktop-data distro

C:\Users\anon>wsl.exe --import rancher-desktop-data C:\Users\anon\AppData\Local\rancher-desktop\rancher-desktop-data "C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\distro-0.27.tar" --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

4. Now open Rancher Desktop, you should see images populate. Add the WSL integration, it should cycle and be stable again.

My machine: Win 11 Pro v 10.0.22621

[JayG-EBSCO]

I'm running into the same problem with Windows 11 Pro, and WSL2. My pc name has a dash in it, is all caps, and I cannot change it as it is managed by the company's IT.

[himani-dangwal]

Did anyone got the issue resolved? My Rancher Desktop suddenly started giving the error 3days back untill then it was working fine 2022-10-28T05:21:09.224Z: WSL failed to execute wsl.exe --unregister rancher-desktop-data: Error: wsl.exe exited with code 4294967295 2022-10-28T05:21:09.224Z: Error setting up data distribution: Error: wsl.exe exited with code 4294967295 at ChildProcess. (C:\Users\XXX\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:1:7750) at ChildProcess.emit (node:events:390:28) at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) { code: 4294967295, command: [ 'wsl.exe', '--unregister', 'rancher-desktop-data' ] } 2022-10-28T05:21:09.285Z: WSL: executing: /bin/sh -c [ -e /etc/os-release ] && . /etc/os-release ; echo ${VERSION_ID:-0.1}: Error: wsl.exe exited with code 4294967295. Even after uninstalling it and then configuring it again it throws the above error

[aggutierrez]

I installed this morning the las Windows 10 cumulative update 21HD2 (KB5019959) and started experiencing this issue. It was fixed after removing the dash from my machine name.

[thi-bezerra]

My error:

Kubernetes Error
Rancher Desktop 1.6.0 - win32 (x64)
Error Starting Kubernetes
Error: UNKNOWN: unknown error, open '\\wsl$\rancher-desktop-data\etc\hosts'
Context:
Updating /etc/hosts

Some recent logfile lines:
2022-10-15T12:09:53.042Z: Error registering data distribution: Error: tar.exe exited with code 128
2022-10-15T12:09:53.072Z: WSL failed to execute wsl.exe --unregister rancher-desktop-data: Error: wsl.exe exited with code 4294967295
2022-10-15T12:09:53.073Z: Error setting up data distribution: Error: wsl.exe exited with code 4294967295
    at ChildProcess.<anonymous> (C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:1:7750)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  code: 4294967295,
  command: [ 'wsl.exe', '--unregister', 'rancher-desktop-data' ]
}

It may not be the same, but I couldn't use Rancher Desktop from a fresh install. For some reason, it's not creating the rancher-desktop-data distro, and I can't get a log output as to why. However, if you manually create these two distros, it will work!

1. Factory reset Rancher Desktop & Shutdown WSL

wsl --shutdown

2. Create the rancher-desktop distro

C:\Users\anon>wsl.exe --import rancher-desktop C:\Users\anon\AppData\Local\rancher-desktop\rancher-desktop "C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\distro-0.27.tar" --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

3. Create the rancher-desktop-data distro

C:\Users\anon>wsl.exe --import rancher-desktop-data C:\Users\anon\AppData\Local\rancher-desktop\rancher-desktop-data "C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\distro-0.27.tar" --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

4. Now open Rancher Desktop, you should see images populate. Add the WSL integration, it should cycle and be stable again.

My machine: Win 11 Pro v 10.0.22621

I had same problem on my Windows 11. If you see the log carefully there is a problem with tar.exe . RancherDesktop expects that a executable tar.exe is available on windows but in my machine was missing. So I downloaded here : http://libarchive.org/ , ranamed the executable bsdtar.exe to tar.exe and add on my path. After that everything worked again.

[torchiaf]

My error is:

Some recent logfile lines:
2023-06-06T15:10:02.042Z: Error registering data distribution: Error: tar.exe exited with code 128
2023-06-06T15:10:02.072Z: WSL failed to execute wsl.exe --unregister rancher-desktop-data: Error: wsl.exe exited with code 4294967295
2023-06-06T15:10:02.073Z: Error setting up data distribution: Error: wsl.exe exited with code 4294967295
    at ChildProcess.<anonymous> (C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:1:7750)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  code: 4294967295,
  command: [ 'wsl.exe', '--unregister', 'rancher-desktop-data' ]
}

In my case, just cleaning up the wsl distros and uninstalling docker-desktop worked.

[iridescent995]

My error:

Kubernetes Error
Rancher Desktop 1.6.0 - win32 (x64)
Error Starting Kubernetes
Error: UNKNOWN: unknown error, open '\\wsl$\rancher-desktop-data\etc\hosts'
Context:
Updating /etc/hosts

Some recent logfile lines:
2022-10-15T12:09:53.042Z: Error registering data distribution: Error: tar.exe exited with code 128
2022-10-15T12:09:53.072Z: WSL failed to execute wsl.exe --unregister rancher-desktop-data: Error: wsl.exe exited with code 4294967295
2022-10-15T12:09:53.073Z: Error setting up data distribution: Error: wsl.exe exited with code 4294967295
    at ChildProcess.<anonymous> (C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:1:7750)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  code: 4294967295,
  command: [ 'wsl.exe', '--unregister', 'rancher-desktop-data' ]
}

It may not be the same, but I couldn't use Rancher Desktop from a fresh install. For some reason, it's not creating the rancher-desktop-data distro, and I can't get a log output as to why. However, if you manually create these two distros, it will work!

1. Factory reset Rancher Desktop & Shutdown WSL

wsl --shutdown

2. Create the rancher-desktop distro

C:\Users\anon>wsl.exe --import rancher-desktop C:\Users\anon\AppData\Local\rancher-desktop\rancher-desktop "C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\distro-0.27.tar" --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

3. Create the rancher-desktop-data distro

C:\Users\anon>wsl.exe --import rancher-desktop-data C:\Users\anon\AppData\Local\rancher-desktop\rancher-desktop-data "C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\distro-0.27.tar" --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

4. Now open Rancher Desktop, you should see images populate. Add the WSL integration, it should cycle and be stable again.

My machine: Win 11 Pro v 10.0.22621

Thanks trevormduncan you are a lifesaver.

[marekhotshot]

My error:

Kubernetes Error
Rancher Desktop 1.6.0 - win32 (x64)
Error Starting Kubernetes
Error: UNKNOWN: unknown error, open '\\wsl$\rancher-desktop-data\etc\hosts'
Context:
Updating /etc/hosts

Some recent logfile lines:
2022-10-15T12:09:53.042Z: Error registering data distribution: Error: tar.exe exited with code 128
2022-10-15T12:09:53.072Z: WSL failed to execute wsl.exe --unregister rancher-desktop-data: Error: wsl.exe exited with code 4294967295
2022-10-15T12:09:53.073Z: Error setting up data distribution: Error: wsl.exe exited with code 4294967295
    at ChildProcess.<anonymous> (C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:1:7750)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  code: 4294967295,
  command: [ 'wsl.exe', '--unregister', 'rancher-desktop-data' ]
}

It may not be the same, but I couldn't use Rancher Desktop from a fresh install. For some reason, it's not creating the rancher-desktop-data distro, and I can't get a log output as to why. However, if you manually create these two distros, it will work!

1. Factory reset Rancher Desktop & Shutdown WSL

wsl --shutdown

2. Create the rancher-desktop distro

C:\Users\anon>wsl.exe --import rancher-desktop C:\Users\anon\AppData\Local\rancher-desktop\rancher-desktop "C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\distro-0.27.tar" --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

3. Create the rancher-desktop-data distro

C:\Users\anon>wsl.exe --import rancher-desktop-data C:\Users\anon\AppData\Local\rancher-desktop\rancher-desktop-data "C:\Users\anon\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\distro-0.27.tar" --version 2
Import in progress, this may take a few minutes.
The operation completed successfully.

4. Now open Rancher Desktop, you should see images populate. Add the WSL integration, it should cycle and be stable again.

My machine: Win 11 Pro v 10.0.22621

this finally worked for me, thanks!

[mook-as]

Unfortunately, this issue appears to have lots of unrelated things and it's not actionable:

• The original issue:

  Error Starting Kubernetes Error:socket hang up

  Unfortunately, the log snippets are irrelevant; we need the full set of log files (preferably with debug mode enabled). They should be attached as files instead of pasted into the comments, as that makes them unreadable.

• A separate issue with hostnames containing dashes (or possibly underscores); it doesn't seem to reproduce, and conversation about this just died on the vine.

• Another issue about tar.exe failing (Error: tar.exe exited with code 128); unfortunately this one also doesn't have the relevant logs.

• WSL failed to execute wsl.exe --unregister rancher-desktop-data: Error: wsl.exe exited with code 4294967295: This is probably a secondary error (since we'd only try to unregister the data distributino if something else already went wrong); however, I don't have adequate logs.

• There's one where C:\Windows\system32\tar.exe is missing. I don't even know how that's possible; that started shipping in Win10 17063, which is way before anything we support. Only thing I can think of is if you have a non-standard minimal install, but I don't think we can support that.

---

Overall, to solve issues, we need:

• One issue per bug. Feel free to create extra issues, we can always link them together afterwards; having multiple bugs in one issue makes it intractable to solve.
• Enable Debug mode before restarting Rancher Desktop to reproduce the issue. If your issue prevents you from getting there, set RD_DEBUG_ENABLED (to 1) in your environment before starting Rancher Desktop.
• Upload all of the log files; copying the snippet from the error dialog is insufficient, as that often doesn't include the extra information we need. There is a link in the error dialog to the logs, if you can't get to the main window.

(Filed #7213 to improve the error dialog to see if we can nudge towards better reports so we can fix the bugs more often.)

[jandubois]

Unfortunately, this issue appears to have lots of unrelated things and it's not actionable:

Given that there is no remaining action that we can take on this, I'm going to close this issue.

If you still have problems, please file a new, separate issue, with all the logs, as requested by @mook-as.