This message was deleted.
# rancher-desktopa
adamant-kite-43734
07/27/2023, 7:01 AMThis message was deleted.
r
rapid-eye-50641
07/27/2023, 2:42 PM@thankful-byte-72527, Can you please share the exact steps and/or manifest files that you used to help us reproduce and understand the behavior? Thanks.
t
thankful-byte-72527
07/27/2023, 2:55 PMSure. There are two pods and a network policy that blocks everything in the default namespace in this example.
thankful-byte-72527
07/27/2023, 2:56 PMRancher Desktop on Windows (not blocked):
Copy code
*wms*EDEV*???*C:\prj\sanity>kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
pod-a 1/1 Running 1 (6h2m ago) 28h 10.42.0.198 logabn220408 <none> <none>
pod-b 1/1 Running 1 (6h2m ago) 28h 10.42.0.193 logabn220408 <none> <none>
*wms*EDEV*???*C:\prj\sanity>kubectl exec pod-a -- curl 10.42.0.193
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 615 100 615 0 0 750k 0 --:--:-- --:--:-- --:--:-- 600k
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<thankful-byte-72527
07/27/2023, 2:58 PMK3s on Ubuntu (blocked):
Copy code
alpha@k3s-alpha:~$ kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
pod-a 1/1 Running 0 30h 10.42.4.156 k3s-delta <none> <none>
pod-b 1/1 Running 0 30h 10.42.2.9 k3s-gamma <none> <none>
alpha@k3s-alpha:~$ kubectl exec pod-a -- curl 10.42.2.9
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 10.42.2.9 port 80 after 0 ms: Couldn't connect to server
command terminated with exit code 7r
rapid-eye-50641
07/27/2023, 2:59 PMThanks you very much for sharing the steps, let me try reproducing on my machine.
rapid-eye-50641
07/27/2023, 3:01 PMAlso, which operating system are you trying this on? Also, is there a specific reason you are still on an older version of Rancher Desktop? Since 1.7.0, We have made a bunch of networking related improvements and It's worth trying the latest 1.9.1 versions and see if it still gives problems.
t
thankful-byte-72527
07/27/2023, 3:04 PM1.9.0 had the habbit of crashing about 1-2 times a day without an error message. I didn't have the time to check why, so I reverted back to the last version that worked for me.
thankful-byte-72527
07/27/2023, 3:05 PMA colleague reported similar issues, so we stopped upgrading for now.
r
rapid-eye-50641
07/27/2023, 4:00 PMOk, Thank you for providing additional context. It would be great if you or one of your colleagues who face issues with the latest version file a Github issue attaching logs from your machine. You can open the folder containing logs via
Troubleshooting > Show Logsf
fast-garage-66093
07/27/2023, 4:37 PMAre you using a proxy? 1.9.0 had updated the https-proxy-agent module, and the new upstream version had a bug. Reverting this upgrade was one of the main reasons for the 1.9.1 patch release. So if your crashes seemed related to proxies, then checking 1.9.1 might still be worthwhile.
t
thankful-byte-72527
07/28/2023, 12:36 PM@fast-garage-66093 Thanks for the info. I'll try it again then since we are using a proxy here
r
rapid-eye-50641
07/28/2023, 3:27 PMI could reproduce the issue as described and do not have any immediate insights to share. So, I am going to file a Github issue for the Rancher Desktop team to investigate this.
rapid-eye-50641
07/28/2023, 3:36 PMHere's the link to the filed bug - https://github.com/rancher-sandbox/rancher-desktop/issues/5247
t
thankful-byte-72527
07/31/2023, 7:37 AMcool, thx
w
worried-kangaroo-36754
09/13/2023, 9:33 AMHI @rapid-eye-50641 "the mysterious colleague" is me.
I mentioned this rd crashing issue here on slack in this thread:
https://rancher-users.slack.com/archives/C0200L1N1MM/p1687790879872709
No luck with finding more details.
Also had no time to investigate further.
That's why i downgraded RD to 1.7 when this issue was not present. I am waiting for new release to check if the issue still exists.
Log files have no details about the crash I was collecting data in ELK from all possible sources.
The issue is present in many dev environments in our organization, but I cannot find any mentions about this online. This looks like some kind of Windows 10 Domain configuration that is colliding with RD.
RD is crashing but WSL still works fine, docker engine works fine. Containers are running, but there is no access to docker api from host.
4 Views