This message was deleted.
# rancher-desktop
a
This message was deleted.
h
Copy code
Rancher Desktop 1.5.0 - win32 (x64)
Error Starting Kubernetes

Error: connect ETIMEDOUT 172.19.230.136:6443

2022-07-28T23:57:35.025Z: Registered distributions: Ubuntu
2022-07-28T23:57:36.473Z: Registered distributions: Ubuntu
2022-07-28T23:57:42.711Z: Registered distributions: Ubuntu,rancher-desktop
2022-07-28T23:57:43.046Z: Registered distributions: Ubuntu,rancher-desktop
2022-07-28T23:57:43.046Z: Creating initial data distribution...
2022-07-28T23:58:01.320Z: Unmounting missing device /dev/sdd: 193 192 8:48 / /mnt/wsl/rancher-desktop/run/data rw,relatime shared:2 - ext4 /dev/sdd rw,discard,errors=remount-ro,data=ordered
2022-07-28T23:58:01.807Z: Did not find a valid mount, mounting /mnt/wsl/rancher-desktop/run/data
2022-07-28T23:58:13.038Z: WSL: executing: cat /root/.docker/config.json: Error: wsl.exe exited with code 1
2022-07-28T23:58:29.256Z: Installing C:\Users\wilboyd\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Users/wilboyd/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ...
nodes were unhealthy complaining about disk so we waiting a while... then finally decided to come post here up once we saw this when describing one of the containers trying to create...
Copy code
Failed to create pod sandbox: rpc error: code = Unknown desc = failed pulling image "<http://k8s.gcr.io|k8s.gcr.io> ││ /pause:3.6": Error response from daemon: Get "<https://k8s.gcr.io/v2/>": net/http: request canceled while waiting for  ││ connection (Client.Timeout exceeded while awaiting headers)
We are attempting to downgrade back to 1.4.1 which is what most of the other folks are on and will report back. One key piece of info is this specific persons machine is quite under powered, 2c/4t and 20gb of RAM vs other devs who have much more modern machines.
w
proxy or vpn situation? did you try the factory reset?
h
VPN, we restarted his machine and got rancher up before the the corp VPN, don't think it's related to 1.5.0 as after we downloaded before we restarted his machine we ran into the same issue/error
so consider this solved for now, apologies for the noise, should have unplugged and plugged things back in before reaching out 🤦
977 Views