rancher-users #rancher-desktop

rancher-desktop

bumpy-truck-18301

08/30/2022, 7:51 PM

I have the same problem as issue #2789. I've been trying to get K8s running with Docker, but only had partial success, so I decided to start over with a clean image and try nerdctl to see if that worked any better. My setup versions are: WSL2, Ubuntu image 22.04, Windows version 21H2 19044.1889, Rancher Desktop 1.5.1 and K8s 1.2.4. I wanted to keep it clean, so I didn't mess with the configuration, just updated and installed net-tools. Given the issues I had previously, install seemed to work best when I had shutdown WSL, so I did that before running the installer. Docker Desktop for Windows was not running during install, or after. ifconfig showed the following and I was able to ping all of the IPv4 addresses, which is a good sign: johnl@DESKTOP-FDQ7CV5:~$ ifconfig cni0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet 10.42.0.1 netmask 255.255.255.0 broadcast 10.42.0.255 inet6 fe80::24a4:48ff:fe03:8d74 prefixlen 64 scopeid 0x20<link> ether 26:a4:48:03:8d:74 txqueuelen 1000 (Ethernet) RX packets 7799 bytes 1590224 (1.5 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8997 bytes 2390098 (2.3 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.21.211.86 netmask 255.255.240.0 broadcast 172.21.223.255 inet6 fe80::215:5dff:fe57:df78 prefixlen 64 scopeid 0x20<link> ether 00:15:5d:57:df:78 txqueuelen 1000 (Ethernet) RX packets 36032 bytes 48580939 (48.5 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5730 bytes 4888506 (4.8 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet 10.42.0.0 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::8c21:34ff:fe02:bbf3 prefixlen 64 scopeid 0x20<link> ether 8e:21:34:02:bb:f3 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 5 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 24491 bytes 9588503 (9.5 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24491 bytes 9588503 (9.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth19feb9db: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet6 fe80::f0c7:5ff:fec4:8363 prefixlen 64 scopeid 0x20<link> ether f2:c7:05:c4:83:63 txqueuelen 0 (Ethernet) RX packets 1331 bytes 126849 (126.8 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1432 bytes 151731 (151.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth861b7861: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet6 fe80::c8f:bff:fec0:6e9 prefixlen 64 scopeid 0x20<link> ether 0e:8f:0b:c0:06:e9 txqueuelen 0 (Ethernet) RX packets 70 bytes 6594 (6.5 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 141 bytes 17002 (17.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb280045d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet6 fe80::242b:cfff:fe97:e683 prefixlen 64 scopeid 0x20<link> ether 26:2b:cf:97:e6:83 txqueuelen 0 (Ethernet) RX packets 4297 bytes 1104056 (1.1 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5137 bytes 821957 (821.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb8af9501: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet6 fe80::1489:1aff:fe2d:9364 prefixlen 64 scopeid 0x20<link> ether 16:89:1a:2d:93:64 txqueuelen 0 (Ethernet) RX packets 1637 bytes 112622 (112.6 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1667 bytes 114870 (114.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethf6daaa16: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet6 fe80::e4c1:4cff:fe22:b51b prefixlen 64 scopeid 0x20<link> ether e6:c1:4c:22:b5:1b txqueuelen 0 (Ethernet) RX packets 1223 bytes 106457 (106.4 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1756 bytes 215304 (215.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 The installation instructions indicate that Helm, kubectl, nerdctl, Moby, Docker Compose will be available after install. When I ran kubectl version, it wasn't found and downloaded the latest version (I hope this doesn't cause issues). Here's the output when I checked on the other apps: johnl@DESKTOP-FDQ7CV5:~/hello-world$ nerdctl build --tag helloworld:v1.0 . WARN[0000] lstat /sys/fs/cgroup/rancher-desktop/run/nerdctl-tmp.986227269/input.1118623100/Dockerfil e: no such file or directory, using Containerfile as fallback FATA[0000] lstat /sys/fs/cgroup/rancher-desktop/run/nerdctl-tmp.986227269/input.1118623100/Container file: no such file or directory johnl@DESKTOP-FDQ7CV5:~/hello-world$ helm version WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/johnl/.kube/config WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/johnl/.kube/config version.BuildInfo{Version:"v3.9.1", GitCommit:"a7c043acb5ff905c261cfdc923a35776ba5e66e4", GitTreeState:"clean", GoVersion:"go1.17.5"} johnl@DESKTOP-FDQ7CV5:~/hello-world$ moby version Command 'moby' not found, did you mean: command 'goby' from deb goby-java (3.3.1+dfsg2-7) Try: sudo apt install <deb name> johnl@DESKTOP-FDQ7CV5:~/hello-world$ docker version The command 'docker' could not be found in this WSL 2 distro. We recommend to activate the WSL integration in Docker Desktop settings. For details about using Docker Desktop with WSL 2, visit: https://docs.docker.com/go/wsl2/ johnl@DESKTOP-FDQ7CV5:~/hello-world$ docker-compose version The command 'docker-compose' could not be found in this WSL 2 distro. We recommend to activate the WSL integration in Docker Desktop settings. For details about using Docker Desktop with WSL 2, visit: https://docs.docker.com/go/wsl2/ johnl@DESKTOP-FDQ7CV5:~$ containerd version Command 'containerd' not found, but can be installed with: sudo apt install containerd Here are the results when I check for the apps in rancher-desktop: ~ # helm version version.BuildInfo{Version:"v3.9.1", GitCommit:"a7c043acb5ff905c261cfdc923a35776ba5e66e4", GitTreeState:"clean", GoVersion:"go1.17.5"} ~ # nerdctl version Client: Version: v0.22.2 OS/Arch: linux/amd64 Git commit: 2899222cb0715f1e5ffe356d10c3439ee8ee3ba4 buildctl: Version: v0.10.3 GitCommit: c8d25d9a103b70dc300a4fd55e7e576472284e31 FATA[0000] cannot access containerd socket "/run/containerd/containerd.sock": no such file or directory ~ # moby version -sh: moby: not found ~ # docker version Client: Version: 20.10.16 API version: 1.41 Go version: go1.18.5 Git commit: aa7e414fdcb23a66e8fabbef0a560ef1769eace5 Built: Tue Aug 2 11:08:17 2022 OS/Arch: linux/amd64 Context: default Experimental: true Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? ~ # docker-compose version The command 'docker-compose' could not be found in this WSL 2 distro. We recommend to activate the WSL integration in Docker Desktop settings. For details about using Docker Desktop with WSL 2, visit: https://docs.docker.com/go/wsl2/ ~ # kubectl version I0830 19:26:05.329229 7689 versioner.go:58] invalid configuration: no configuration has been provided I0830 19:26:05.333519 7689 versioner.go:64] No local kubectl binary found, fetching latest stable release version I0830 19:26:05.627855 7689 versioner.go:84] Right kubectl missing, downloading version 1.25.0 Downloading https://storage.googleapis.com/kubernetes-release/release/v1.25.0/bin/linux/amd64/kubectl kubectl1.25.0 100% |████████████████████████████████████████| (45/45 MB, 29.381 MB/s) [1s:0s] done. WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version. Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.0", GitCommit:"a866cbe2e5bbaa01cfd5e969aa3e033f3282a8a2", GitTreeState:"clean", BuildDate:"2022-08-23T17:44:59Z", GoVersion:"go1.19", Compiler:"gc", Platform:"linux/amd64"} Kustomize Version: v4.5.7 The connection to the server localhost:8080 was refused - did you specify the right host or port? (NOTE: I didn't get the localhost error after kubectl was installed on Ubuntu; everything else was the same) Do we need to copy, link, or manually install these apps? Please provide details. Thanks, John

handsome-jewelry-53515

08/31/2022, 3:05 AM

Are you running the rancher-desktop app during your testing? The links required are setup as the app initializes. If you are running the app, are you seeing any errors on the app?

little-accountant-66169

08/31/2022, 3:58 AM

Hello, posted in general, but as it is related to docker desktop will post here. Installed rancher desktop. Tried running my compose files after installing, but I get error

time="2022-08-31T09:23:43+09:00" level=fatal msg="cannot access containerd socket \"\\\\\\\\.\\\\pipe\\\\containerd-containerd\": open \\\\.\\pipe\\containerd-containerd: The system cannot find the file specified."

How do I resolve this issue?

worried-activity-29498

08/31/2022, 8:00 AM

Good morning everyone, I am very new to Rancher Desktop as a matter fact I am installing it right now. Are there any tutorials out there either videos/articles I can read to learn it?

ripe-petabyte-15925

08/31/2022, 12:29 PM

Hello, I am experiencing this issue with RD on Windows 10

- I have pointed Docker Registry to our private repository in .m2/setting.xml.

• Now when I try to build images from the docker file, things work fine when the images are fetched from private repo

• But there is another requirement where we use base image from public docker hub [docker/io] repository and now when i try to build the image, its searching in private repo and not falling back to docker hub

• Earlier when docker registry was not pointing to private repo then it was searching/fetching in/from docker hub

• Also, when i pull the base image say nginx from command line > docker pull nginx it works abs fine

• Not sure what and how RD needs to be told - if the image not found in private repo search docker hub

icy-garage-31078

08/31/2022, 4:17 PM

Is it possible to configure the mac address (or ip) for the bridged adapter in Rancher Desktop (More precisely LIMA)? I'm running into an issue where my internal network is the same range as my corporate VPN, so all traffic keeps getting sent across it. I'm wondering if I can get around this by simply forcing the assignment somehow. (Ref https://rancher-users.slack.com/archives/C0200L1N1MM/p1661264570387719)

worried-activity-29498

09/01/2022, 9:12 AM

Good Morning Guys

future-keyboard-11621

09/01/2022, 10:49 AM

My custom

hosts

file entries dont resolve into the cluster most of the time. I am running rancher desktop on m1, sometimes it takes a few hours for ranchers core-dns? to update and start resolving the address properly thats set in

/etc/hosts

rich-musician-88417

09/01/2022, 12:55 PM

Hi. I'm trying to access to containerd (or docker/moby)-API via TCP from the windows command line (or via the gradle-docker-plugin from our build files). But the connection to tcp://localhost:2375 is refused. If tried to change the sockets/hosts via /etc/docker/daemon.json but then i run into https://github.com/rancher-sandbox/rancher-desktop/discussions/2304. Is there any way to achieve remote access to containerd/docker with Rancher-Desktop, ideally without TLS at least for local connections?

modern-pilot-62631

09/02/2022, 7:00 PM

Hi Folks I am new to Rancher-desktop and am currently using in windows with wsl2. I have added the wsl ubuntu distribution as I need more tools that it provides. I have noticed that commands seem to be noticeably slower that if I do the same in powershell. I have turned on integration with the distro in Rancher-desktop but was wondering if there are any guides on tweaking the performance out there. Thanks

orange-tent-50778

09/02/2022, 8:40 PM

I am running RD 1.5.1 on Ubuntu 22.04. When I try to display the Dashboard, it shows a blank screen. I had uninstalled it previously and reinstalled it. I followed the instructions in the Troubleshooting section and reset to factory defaults but still no dashboard. My only non-default setting is I have disabled Traefik. I searched through this channel and see that some others have had this problem when they uninstalled RD. They had to manually remove some files. These were all on Windows and I did not see a list of files that should be cleaned out. If I start RD from the command line, I see the following error messages when I then try to display the dashboard:

(node:11886) electron: Failed to load URL: <http://127.0.0.1:9080/dashboard/c/local/explorer> with error: ERR_CONNECTION_REFUSED

I have a separate Ubuntu 22.04 system where the Dashboard is displayed with no problem. Any thoughts?

gifted-wall-83531

09/04/2022, 12:05 AM

Hi: I use RD 1.5.1, WhenI installed RD and the following error appeared after startup RD. FailedCreatePodSandBox (23)32 secs agoFailed to create pod sandbox: rpc error: code = Unknown desc = failed pulling image "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) And I can't access to "k8s.gcr.io", Is there any solution? Thanks!

best-wall-17038

09/04/2022, 9:47 PM

Hi, When I use nginx ingress controller in rancher-desktop what should be the hostname ? I am getting an error when I would like to use IP i`s invalid: spec.rules[0].host: Invalid value: "192.168.178.38": must be a DNS name, not an IP address`

kubectl get svc -n nginx                                                                                                                                                                                                                                                                                                                              
NAME                  TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)                      AGE
nginx-nginx-ingress   LoadBalancer   10.43.49.252   192.168.178.38   80:32277/TCP,443:32004/TCP   50d

stale-actor-21884

09/05/2022, 12:14 AM

2022-09-04T23:56:58.773Z: Rejected cert expired on Sun, 23 Oct 2011 14:14:14 GMT issued by A-CERT ADVANCED
2022-09-04T23:56:58.773Z: Rejected cert expired on Sun, 30 Nov 2014 23:00:00 GMT issued by A-Trust-Qual-01
2022-09-04T23:56:58.774Z: Rejected cert expired on Tue, 24 Apr 2018 22:00:00 GMT issued by A-Trust-Qual-03
2022-09-04T23:56:58.774Z: Rejected cert expired on Sun, 30 Nov 2014 23:00:00 GMT issued by A-Trust-nQual-01
2022-09-04T23:56:58.774Z: Rejected cert expired on Mon, 17 Aug 2015 22:00:00 GMT issued by A-Trust-nQual-03
2022-09-04T23:56:58.774Z: Rejected cert expired on Sun, 03 Nov 2019 16:17:45 GMT issued by AC1 RAIZ MTIN
2022-09-04T23:56:58.777Z: Rejected cert expired on Tue, 30 Nov 2021 23:00:00 GMT issued by ANF Server CA
2022-09-04T23:56:58.777Z: Rejected cert expired on Sat, 25 Jun 2022 14:06:00 GMT issued by Actalis Authentication CA G1
2022-09-04T23:56:58.777Z: Rejected cert expired on Sat, 30 May 2020 10:48:38 GMT issued by AddTrust External CA Root
2022-09-04T23:56:58.778Z: Rejected cert expired on Wed, 10 Nov 2021 07:51:07 GMT issued by Admin-Root-CA
2022-09-04T23:56:58.778Z: Rejected cert expired on Mon, 25 Jan 2016 12:36:19 GMT issued by AdminCA-CD-T01
2022-09-04T23:56:58.779Z: Rejected cert expired on Wed, 30 Nov 2011 23:59:00 GMT issued by Autoridade Certificadora Raiz Brasileira
2022-09-04T23:56:58.779Z: Rejected cert expired on Thu, 29 Jul 2021 19:17:10 GMT issued by Autoridade Certificadora Raiz Brasileira v1
2022-09-04T23:56:58.780Z: Rejected cert expired on Tue, 22 Mar 2016 01:39:34 GMT issued by CA Disig
2022-09-04T23:56:58.781Z: Rejected cert expired on Sat, 04 Jul 2015 07:02:48 GMT issued by CCA India 2007
2022-09-04T23:56:58.781Z: Rejected cert expired on Fri, 11 Mar 2016 06:48:52 GMT issued by CCA India 2011
2022-09-04T23:56:58.781Z: Rejected cert expired on Wed, 03 Mar 2010 14:59:59 GMT issued by CertRSA01
2022-09-04T23:56:58.782Z: Rejected cert expired on Sun, 26 Jul 2020 10:00:00 GMT issued by Certipost E-Trust Primary Normalised CA
2022-09-04T23:56:58.782Z: Rejected cert expired on Sun, 26 Jul 2020 10:00:00 GMT issued by Certipost E-Trust Primary Qualified CA
2022-09-04T23:56:58.783Z: Rejected cert expired on Wed, 15 Dec 2021 08:00:00 GMT issued by Cybertrust Global Root
2022-09-04T23:56:58.783Z: Rejected cert expired on Fri, 08 Jun 2012 11:47:46 GMT issued by D-TRUST Qualified Root CA 1 2007:PN
2022-09-04T23:56:58.784Z: Rejected cert expired on Mon, 16 May 2022 05:20:47 GMT issued by D-TRUST Root Class 2 CA 2007
2022-09-04T23:56:58.784Z: Rejected cert expired on Mon, 16 May 2022 05:20:47 GMT issued by D-TRUST Root Class 3 CA 2007
2022-09-04T23:56:58.785Z: Rejected cert expired on Sat, 25 May 2019 16:39:40 GMT issued by <http://Entrust.net|Entrust.net> Secure Server Certification Authority
2022-09-04T23:56:58.786Z: Rejected cert expired on Wed, 15 Mar 2017 06:00:04 GMT issued by GPKIRootCA
2022-09-04T23:56:58.786Z: Rejected cert expired on Sat, 21 May 2022 04:00:00 GMT issued by GeoTrust Global CA
2022-09-04T23:56:58.786Z: Rejected cert expired on Mon, 04 Mar 2019 05:00:00 GMT issued by GeoTrust Global CA 2
2022-09-04T23:56:58.787Z: Rejected cert expired on Fri, 05 Jun 2020 10:33:31 GMT issued by Halcom CA FO
2022-09-04T23:56:58.787Z: Rejected cert expired on Thu, 07 Feb 2019 18:33:31 GMT issued by Halcom CA PO 2
2022-09-04T23:56:58.787Z: Rejected cert expired on Sun, 01 Sep 2019 00:00:00 GMT issued by I.CA - Qualified Certification Authority, 09/2009
2022-09-04T23:56:58.787Z: Rejected cert expired on Sun, 01 Apr 2018 00:00:00 GMT issued by I.CA - Qualified root certificate
2022-09-04T23:56:58.788Z: Rejected cert expired on Sun, 01 Sep 2019 00:00:00 GMT issued by I.CA - Standard Certification Authority, 09/2009
2022-09-04T23:56:58.788Z: Rejected cert expired on Sun, 01 Apr 2018 00:00:00 GMT issued by I.CA - Standard root certificate
2022-09-04T23:56:58.788Z: Rejected cert expired on Sat, 17 Oct 2020 14:29:22 GMT issued by IGC/A
2022-09-04T23:56:58.788Z: Rejected cert expired on Tue, 12 Dec 2017 15:00:00 GMT issued by ApplicationCA
2022-09-04T23:56:58.788Z: Rejected cert expired on Tue, 26 May 2020 00:00:00 GMT issued by KEYNECTIS ROOT CA
2022-09-04T23:56:58.788Z: Rejected cert expired on Wed, 19 Nov 2014 06:39:51 GMT issued by KISA RootCA 3
2022-09-04T23:56:58.788Z: Rejected cert expired on Thu, 31 Mar 2016 14:59:59 GMT issued by Application CA G2
2022-09-04T23:56:58.788Z: Rejected cert expired on Wed, 17 Mar 2021 09:51:37 GMT issued by LuxTrust Global Root
2022-09-04T23:56:58.788Z: Rejected cert expired on Tue, 29 Jan 2013 23:59:59 GMT issued by Macao Post eSignTrust Root Certification Authority
2022-09-04T23:56:58.789Z: Rejected cert expired on Sun, 05 Jan 2020 23:59:59 GMT issued by Macao Post eSignTrust Root Certification Authority (G02)
2022-09-04T23:56:58.789Z: Rejected cert expired on Thu, 06 Apr 2017 12:28:44 GMT issued by Microsec e-Szigno Root CA
2022-09-04T23:56:58.789Z: Rejected cert expired on Thu, 31 Dec 2020 07:00:00 GMT issued by Microsoft Root Authority
2022-09-04T23:56:58.789Z: Rejected cert expired on Sun, 09 May 2021 23:28:13 GMT issued by Microsoft Root Certificate Authority
2022-09-04T23:56:58.790Z: Rejected cert expired on Fri, 20 Aug 2010 13:56:21 GMT issued by Post.Trust Root CA
2022-09-04T23:56:58.790Z: Rejected cert expired on Wed, 17 Mar 2021 18:33:33 GMT issued by QuoVadis Root Certification Authority
2022-09-04T23:56:58.791Z: Rejected cert expired on Sat, 21 Apr 2012 09:07:23 GMT issued by Root CA
2022-09-04T23:56:58.791Z: Rejected cert expired on Thu, 01 Jul 2021 15:22:47 GMT issued by Root CA Generalitat Valenciana
2022-09-04T23:56:58.791Z: Rejected cert expired on Sat, 28 Nov 2015 06:02:38 GMT issued by SITHS CA v3
2022-09-04T23:56:58.792Z: Rejected cert expired on Wed, 16 Dec 2015 09:15:38 GMT issued by Staat der Nederlanden Root CA
2022-09-04T23:56:58.792Z: Rejected cert expired on Wed, 25 Mar 2020 11:03:10 GMT issued by Staat der Nederlanden Root CA - G2
2022-09-04T23:56:58.794Z: Rejected cert expired on Mon, 05 Apr 2021 17:03:17 GMT issued by TDC Internet Root CA
2022-09-04T23:56:58.795Z: Rejected cert expired on Fri, 01 Jan 2021 23:59:59 GMT issued by Thawte Premium Server CA
2022-09-04T23:56:58.795Z: Rejected cert expired on Fri, 01 Jan 2021 23:59:59 GMT issued by Thawte Server CA
2022-09-04T23:56:58.795Z: Rejected cert expired on Mon, 21 Aug 2017 11:37:07 GMT issued by TÃBÄ°TAK UEKAE KÃ¶k Sertifika Hizmet SaÄlayÄ±cÄ±sÄ± - SÃ¼rÃ¼m 3
2022-09-04T23:56:58.795Z: Rejected cert expired on Wed, 16 Sep 2015 10:07:57 GMT issued by TÃRKTRUST Elektronik Sertifika Hizmet SaÄlayÄ±cÄ±sÄ±
2022-09-04T23:56:58.796Z: Rejected cert expired on Tue, 09 Jul 2019 18:40:36 GMT issued by UTN-USERFirst-Object
2022-09-04T23:56:58.796Z: Rejected cert expired on Wed, 04 Jan 2017 11:32:48 GMT issued by e-Guven Kok Elektronik Sertifika Hizmet Saglayicisi
2022-09-04T23:56:58.797Z: Rejected cert expired on Tue, 29 Jun 2021 21:57:46 GMT issued by sigen-ca
2022-09-04T23:56:58.799Z: mainEvents settings-update: {"version":4,"kubernetes":{"version":"1.20.15","memoryInGB":6,"numberCPUs":2,"port":6443,"containerEngine":"moby","checkForExistingKimBuilder":false,"enabled":true,"WSLIntegrations":{},"options":{"traefik":true,"flannel":true},"suppressSudo":false,"hostResolver":true},"portForwarding":{"includeKubernetesServices":false},"images":{"showAll":true,"namespace":"<http://k8s.io|k8s.io>"},"telemetry":true,"updater":false,"debug":false,"pathManagementStrategy":"rcfiles"}
2022-09-05T00:01:44.386Z: Kubernetes was unable to start: Error: /opt/rancher-desktop/resources/resources/linux/lima/bin/limactl exited with code 1
    at ChildProcess.<anonymous> (/opt/rancher-desktop/resources/app.asar/dist/app/background.js:17:142946)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  stdout: 'Directory /home/madhurakuppal/.cache/rancher-desktop/k3s/v1.20.15+k3s1 does not exist\n',
  stderr: '',
  code: 1,
  command: [
    '/opt/rancher-desktop/resources/resources/linux/lima/bin/limactl',
    'shell',
    '--workdir=.',
    '0',
    'sudo',
    'bin/install-k3s',
    'v1.20.15+k3s1',
    '/home/madhurakuppal/.cache/rancher-desktop/k3s'
  ]
}

icy-gpu-52918

09/06/2022, 11:39 AM

Hello i have a rancher destkop question. i cant get docker cli working --> Get "http://0.0.0.0:2375/v1.24/containers/json": dial tcp 0.0.0.0:2375: connectex: No connection could be made because the target machine actively refused it. Using nerdctl i have no issues

future-keyboard-11621

09/06/2022, 12:23 PM

How would I debug slow requests within the cluster? • Some requests from the pod to the internet with CURL can take 8 seconds. • Everything works great if I increase the timeout to infinite, but thats not really a solution. • same requests take no time on the host computer • dig returns 3ms

fast-garage-66093

09/06/2022, 5:27 PM

If nobody is able to help you on Slack, then it would be best to open a Github issue about it.

👍 1

future-keyboard-11621

09/07/2022, 8:47 AM

I am getting 8 seconds when requesting from the cluster a website with curl. 🤔

best-wall-17038

09/07/2022, 9:21 AM

In rancher why I can not able to access my frontend app through External-IP?

kubectl get svc -n nginx -o wide                                                                                                                                                                                                                                                                                                                    
NAME                  TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)                      AGE   SELECTOR
nginx-nginx-ingress   LoadBalancer   10.43.49.252   192.168.178.38   80:32277/TCP,443:32004/TCP   52d   app=nginx-nginx-ingress

When I added localhost as a host, I can access over localhost but this is not something i wanter

apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
  name: {{ include "frontend-service.fullname" . }}
  namespace: comnext
  annotations:
    <http://nginx.ingress.kubernetes.io/service-upstream|nginx.ingress.kubernetes.io/service-upstream>: "true"
    <http://nginx.ingress.kubernetes.io/use-regex|nginx.ingress.kubernetes.io/use-regex>: "true"
    <http://ingress.kubernetes.io/rewrite-target|ingress.kubernetes.io/rewrite-target>: /$1
    <http://nginx.ingress.kubernetes.io/configuration-snippet|nginx.ingress.kubernetes.io/configuration-snippet>: |
      proxy_set_header l5d-dst-override frontend-service.comnext.svc.cluster.local;
      proxy_hide_header l5d-remote-ip;
      proxy_hide_header l5d-server-id;
spec:
  ingressClassName: nginx
  rules:
    - host: localhost
      http:
        paths:
          - backend:
              service:
                name: frontend-service
                port:
                  number: 80
            path: /
            pathType: ImplementationSpecific

best-wall-17038

09/07/2022, 10:27 AM

Why my frontend service can not access backend-services through their service name(DNS) in rancher-desktop 😕

early-receptionist-44710

09/07/2022, 4:37 PM

'time="2022-09-07T11:35:42-05:00" level=fatal msg="networks.yaml field `paths.sudoers` error: dir \\"/private/etc\\" is world-writable"\n',
  code: 1,
  command: [
    '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
    'start',
    '--tty=false',
    '/Users/me/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
  ]
}

Anyone know how to get around this ?

early-receptionist-44710

09/07/2022, 4:44 PM

sudo chmod 775 /private/etc

SOLVED ✅

👍 1

broad-train-31975

09/08/2022, 1:47 AM

Thanks a lot, I’ve spent quite a while reading Rancher Desktop sources and turned to this Slack channel as a last resort. Worked like a charm for me. I quit Rancher Desktop app and started it again for the change to take effect. Is there a better option, @fast-garage-66093?

early-shoe-8160

09/08/2022, 2:12 AM

Hello everyone I just have a quick question, I've tried to delete unused images via rancher desktop UI but after that, I noticed that I still haven't reclaimed disk space for it. But when I reset all my rancher configs, I get the free space back. Any thoughts?

best-wall-17038

09/08/2022, 8:34 AM

Hello, Since yesterday rancher-desktop is not running properly in my macOS.. I am getting below error, when I restart rancher-desktop its working but then again started to get this error.What might be the reason of this ?

kubectl get pods -n comnext                                                                                                                                                                                                                                                                                                            
I0908 10:32:01.731836   12084 versioner.go:56] Remote kubernetes server unreachable
Unable to connect to the server: net/http: TLS handshake timeout

witty-flower-16290

09/08/2022, 2:50 PM

is there something obvious im missing but when i change the resource values in preferences for cpu usage etc my qemu process is ALWAYS locked to a single core...e

clever-pillow-66654

09/08/2022, 4:15 PM

I’m trying to debug some issues with an application, but as part of this I noticed some odd networking behaviour macOS ventura (also occurs on monterey) rancher 1.5.1 containerd

nerdctl run -it --rm alpine

then run

ping 8.8.8.8

. I see:

/ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=254 time=3166643.804 ms
64 bytes from 8.8.8.8: seq=0 ttl=254 time=3167642.102 ms (DUP!)
64 bytes from 8.8.8.8: seq=0 ttl=254 time=3168662.359 ms (DUP!)
64 bytes from 8.8.8.8: seq=0 ttl=254 time=3169650.931 ms (DUP!)
64 bytes from 8.8.8.8: seq=0 ttl=254 time=3170643.970 ms (DUP!)

This looks like a networking issue. Any ideas? A colleague is seeing the same. We originally saw within an app container

fast-airline-86487

09/09/2022, 3:30 AM

This doesn’t seem quite right to me. Is this intentional?

~/.docker/cli-plugins/docker-buildx

is symlinked to

/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/docker-buildx|Desktop.app/Contents/Resources/resources/darwin/docker-buildx>

It is missing the

/bin

in it. Interestingly, on my work mac,

~/.docker/cli-plugins/

has symlinks to

~/.rd/bin/

(RD 1.5.1 on both). As a result,

docker buildx

is failing with

Invalid Plugins

fresh-football-21032

09/09/2022, 5:54 AM

Hello Fellow Ranchers, I am using Rancher Version: 1.5.1 on Windows 11. When connected to my office VPN . The Rancher Desktop does not come up and shows k8s error

Kubernetes Error
Rancher Desktop 1.5.1 - win32 (x64)
Error Starting Kubernetes
Error: connect ETIMEDOUT 172.50.103.131:6443
Context:
Waiting for nodes

I have tried the wsl-vpnkit that many have suggested but it does not seem to work. Do we have any updates on this issue? In this channel also have seen this getting raised but don't think it's resolved yet..

hallowed-island-45301

09/09/2022, 11:29 PM

Hello! New Rancher Desktop user here. I like how I can easily switch between K8s versions in RD, but I’m wondering if I can use RD to manage multiple clusters for the same K8s version? For example, I want to be able to switch my context from one 1.24.3 cluster to a new 1.24.3 cluster, without having to reset the former. I don’t need both versions running at the same time, I’m just looking for a way to get a “clean” environment without blowing away something I want to come back to later.

Title

hallowed-island-45301

09/09/2022, 11:29 PM

fast-garage-66093

09/09/2022, 11:38 PM

This is not supported by RD itself. I believe you can do this from the commandline by switching RD to use the moby engine, and then use k3d to create / suspend clusters inside docker.

k3d

hallowed-island-45301

09/10/2022, 1:52 AM

Ok, thanks!

View count: 18