Hi, I'm trying to use the port-forwarding option on the Rancher Desktop GUI to forward messages from my local machine, i.e. localhost, to my rancher kubernetes cluster. When I run the "kubectl port forward <service> <localport>:<clusterport>" on the command line from my local machine it communicates with the cluster fine but the port forwarding on Rancher Desktop, given the same connection details doesn't work. Can anyone shed any light on this?

Rancher Desktop on Mac M1 (SUSE Managed) - Deploying or importing EKS Clusters with default settings from Rancher UI always results in: [Disconnected] Cluster agent is not connected Waiting for API to be available

It appears Provisioning Scripts on Windows are not being run because they cannot be found. Looking at the logs no files are found when it attempts to execute

wsl.exe --distribution rancher-desktop --exec /usr/bin/find /etc/local.d ( -name *.start -o -name *.stop ) -print -exec chmod a+x {}

. When I manually execute

wsl.exe --distribution rancher-desktop --exec /usr/bin/find /etc/local.d -name *.start -print

it finds nothing. However, when I execute

wsl.exe --distribution rancher-desktop --exec /usr/bin/find /etc/local.d/ -name *.start -print

(notice the trailing

/

) it returns the .start provisioning script. Has anyone else run into this?

Hello all, I'm new to rancher-desktop. I'm working for a corporation that has a mandatory VPN and corporate proxy. I've been having trouble getting rancher-desktop to replace docker-desktop at this point, I'd love to use Rancher especially since we are planning on using k3s when going to prod so hoping to keep development as close to prod as possible. I was originally running into ks3 startup issues, but that has been resolved with 1.8.1 and the experimental gviser network tunnel. I'm now running into timeout issues when doing and docker pull or really any network command from the wsl vm. I was assuming this is proxy related, I tried setting WSLENV for http_proxy and https_proxy but unfortunately our corporate proxy isn't TLS so that again causes k3s to not start. Any other workarounds for this issue?

Does anyone know or can help me on how to solve this problem?

hi team , I installed latest Rancher without any issue while I run cmd docker images and got error

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

anyone could help me?

Hi everyone! I'm trying to install Keyloack as an OIDC provider in Rancher Desktop but I need to configure the api server to accept keycloak as an oidc-issuer: how can I do it with Rancher Desktop?

Good morning! I'm making the switch from docker to rancher and I've got things mostly up and running but my mariadb container is failing with the following error. This worked fine under docker so I'm not sure what might have changed.

chown: changing ownership of '/var/lib/mysql': Permission denied

Hi Team, I'm trying to run Aerospike using Rancher desktop nerdctl and its giving me error

CRITICAL (config): (cfg.c:4105) 1024 system file descriptors not enough, config specified 15000

Even I tired overriding the limit as mentioned in this link.

I would like to change my current Mac dev environment over to use Rancher Desktop, but I’m running into two issues: 1. a hanging condition trying to run some build tooling for the Istio open source project. Not sure the best way to proceed. To create the hang, isn’t too difficult. You can simply clone the istio repo,

git clone <https://github.com/istio/istio.git>

and try running a

make build

. It hangs pretty early in that process. 2. within the tooling container we also run docker commands (DinD) to the mounted socket. It seems Rancher Desktop doesn’t like to do that in a rootless container. If running the container as root, things work. Simply command to verify:

docker run -v /var/run/docker.sock:/var/run/docker.sock -u 501: -it --rm docker docker ps

. Remove the -u parm and it should work.

Hi I switched to rancher-desktop and I'm trying to run my docker-compose but I'm receiving an error

hi! I have a problem with running rancher-desktop on a policy-heavy corpo system while starting it shows that

Error Starting kubernetes
  Certificate validation error: CERT_SIGNATURE_FAILURE

could anyone help me with this?

hey all, trying to install Rancher Desktop on M2 silicone, and having trouble getting the docker daemon to run. It is stuck in

Waiting for image manager to be ready

after the automated configuration for

moby

after a fresh install. Thoughts? Thread in #general

@billowy-baker-61557 has left the channel

Hello, I had docker desktop installed and I have uninstalled it. After that, I installed rancher desktop v1.81 on windows 10 and it works fine when I use containerd, but, when I use dockerd, any docker command I use return the following error message error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json": open //./pipe/docker_engine: The system cannot find the file specified. I tried to uninstall rancher desktop and reinstall it but every time it returns same error message any help will be appreciated.

Hello just switched from docker desktop to rancher desktop. If from a folder like this

C:\Users\Ivan.Compagnoni\Progetti\wiremock-tests

I try to run a command to mount a volume

docker run -it --rm -p 8080:8080 --name wiremock -v /c/Users/Ivan.Compagnoni/Progetti/wiremock-tests/:/home/wiremock wiremock/wiremock:2.35.0

I received an error: Error response from daemon: make cli opts(): making volume mountpoint for volume /c/Users/Ivan.Compagnoni/Progetti/wiremock-tests/: mkdir /c: permission denied. Not sure how to debug the problem. I'm using it on Windows 10 with WSL and I've tryed both with moby and containerd but the problem seems the same.

Hi I'm using Rancher Desktop 1.9.0-tech-preview in Windows WSL2 and have one pod that isn't able to reach the other through the Service IP. Only works if using the Pod IP.

jnsilva@jorge-silva:~$ kubectl get pod -n t54 -o wide
NAME                                READY   STATUS      RESTARTS      AGE   IP            NODE          NOMINATED NODE   READINESS GATES
ipostgresql-client-20230510192650   0/1     Completed   0             15h   10.42.0.232   jorge-silva   <none>           <none>
t54-rafm-process-mqcgj              0/1     Completed   0             15h   10.42.0.234   jorge-silva   <none>           <none>
postgresql-t54-0                    1/1     Running     1 (10m ago)   15h   10.42.0.247   jorge-silva   <none>           <none>
t54-rafm-0                          1/1     Running     2 (10m ago)   15h   10.42.0.242   jorge-silva   <none>           <none>
jnsilva@jorge-silva:~$ kubectl get svc -n t54 -o wide
NAME                TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE   SELECTOR
postgresql-t54-hl   ClusterIP   None           <none>        5432/TCP    15h   <http://app.kubernetes.io/component=primary,app.kubernetes.io/instance=postgresql-t54,app.kubernetes.io/name=postgresql|app.kubernetes.io/component=primary,app.kubernetes.io/instance=postgresql-t54,app.kubernetes.io/name=postgresql>
postgresql-t54      ClusterIP   10.43.27.71    <none>        5432/TCP    15h   <http://app.kubernetes.io/component=primary,app.kubernetes.io/instance=postgresql-t54,app.kubernetes.io/name=postgresql|app.kubernetes.io/component=primary,app.kubernetes.io/instance=postgresql-t54,app.kubernetes.io/name=postgresql>
t54                 ClusterIP   10.43.14.118   <none>        40353/TCP   15h   <http://app.kubernetes.io/instance=t54-rafm,app.kubernetes.io/name=rafm|app.kubernetes.io/instance=t54-rafm,app.kubernetes.io/name=rafm>
jnsilva@jorge-silva:~$ kubectl get pod -n portal
NAME                                READY   STATUS      RESTARTS      AGE
ipostgresql-client-20230510190418   0/1     Completed   0             15h
portal-process-xfsnl                0/1     Completed   0             15h
postgresql-portal-0                 1/1     Running     1 (11m ago)   15h
portal-7cf887ccb7-pp7t8             1/1     Running     2 (10m ago)   15h
jnsilva@jorge-silva:~$ kubectl exec -it portal-7cf887ccb7-pp7t8 -n portal sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
Defaulted container "portal" out of: portal, volume-permissions (init)
bash-5.1$ wget <http://t54.t54.svc.cluster.local:40353/xdt/>
--2023-05-11 10:00:26--  <http://t54.t54.svc.cluster.local:40353/xdt/>
Resolving t54.t54.svc.cluster.local (t54.t54.svc.cluster.local)... 10.43.14.118
Connecting to t54.t54.svc.cluster.local (t54.t54.svc.cluster.local)|10.43.14.118|:40353... ^C
bash-5.1$
bash-5.1$
bash-5.1$ wget <http://10.42.0.242:40353/xdt/>
--2023-05-11 10:01:32--  <http://10.42.0.242:40353/xdt/>
Connecting to 10.42.0.242:40353... connected.
HTTP request sent, awaiting response... 200 OK
Length: 40
Saving to: 'index.html'

index.html                                             100%[=========================================================================================================================>]      40  --.-KB/s    in 0s

2023-05-11 10:01:32 (10.3 MB/s) - 'index.html' saved [40/40]

bash-5.1$ exit
exit

Hi, thinking of giving Rancher Desktop a spin on my Windows 10 (Enterprise) PC. The Installation instructions say that WSL would be installed when installing it. However, what is the behaviour if WSL2 is already installed and I have 2 other WSL distros installed (Ubuntu 22.04 and Alpine) ? I'd expect RD installer to skip the WSL2 installation part, leaving my existing distros untouched and installing only the distro needed for RD. Also if I were to uninstall Rancher Desktop, would it leave the WSL2 and my other 2 distros behind untouched ?

Hello, there is an error in log file "wsl-helper.log" saying: Error: could not detect WSL2 VM: could not find WSL2 VM ID: could not dial VM 3356AFB4-773B-4021-8E78-7DBEA36F76FE: could not dial Hyper-V socket: connect(3356afb4-773b-4021-8e78-7dbea36f76fe:00001f91-facb-11e6-bd58-64006a7986d3) failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. and docker images command returns the following error error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json": open //./pipe/docker_engine: The system cannot find the file specified. I am using Rancher Desktop v1.8.1 any help will be appreciated.

I am running Rancher Desktop v1.8.1 on Mac Big Sur. I can't start Rancher due to 'No space left on device' error. When I start Rancher desktop, it doesn't start any containers.

stderr: 'scp: /tmp/rd-nerdctl-maUYHq.nerdctl: No space left on device\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>',
    'copy',
    '/var/folders/w5/zd3mhbp553l27m7djjd450ph0000gn/T/rd-nerdctl-maUYHq/nerdctl',
    '0:/tmp/rd-nerdctl-maUYHq.nerdctl'
  ]
}

Any idea why?

Filesystem       Size   Used  Avail Capacity iused      ifree %iused  Mounted on
/dev/disk1s1s1  466Gi   14Gi  137Gi    10%  553797 4881899083    0%   /
devfs           190Ki  190Ki    0Bi   100%     658          0  100%   /dev
/dev/disk1s5    466Gi   24Ki  137Gi     1%       0 4882452880    0%   /System/Volumes/VM
/dev/disk1s3    466Gi  734Mi  137Gi     1%    2864 4882450016    0%   /System/Volumes/Preboot
/dev/disk1s6    466Gi  5.4Mi  137Gi     1%      15 4882452865    0%   /System/Volumes/Update
/dev/disk1s2    466Gi  312Gi  137Gi    70% 1030785 4881422095    0%   /System/Volumes/Data
map auto_home     0Bi    0Bi    0Bi   100%       0          0  100%   /System/Volumes/Data/home

I got this error trying to start Kubernetes on Rancher Desktop v1.8.1 on M1:

Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1

Hi everybody hoping i can get a little assistance on an issue i'm experiencing. I'm running on a M1 Mac with Rancher 1.8.1, and I have given rancher desktop full disk access. (this all works for my other team member who are running colima) I'm following this guide https://medium.com/platform-engineer/running-aws-dynamodb-local-with-docker-compose-6f75850aba1e using the 1.2 (docker compose way) section

version: '3.7'
services:
  dynamodb:
    image:  amazon/dynamodb-local
    container_name: my-dynamodb
    hostname: dynamodb
    restart: always
    volumes:
      -  ./my-dynamodb-data:/home/dynamodblocal/data
    ports:
      - 8100:8000
    command: "-jar DynamoDBLocal.jar -sharedDb -dbPath /home/dynamodblocal/data/"

i run my docker compose and i get the following:

Attaching to my-dynamodb
my-dynamodb  | Initializing DynamoDB Local with the following configuration:
my-dynamodb  | Port:    8000
my-dynamodb  | InMemory:        false
my-dynamodb  | DbPath:  /home/dynamodblocal/data/
my-dynamodb  | SharedDb:        true
my-dynamodb  | shouldDelayTransientStatuses:    false
my-dynamodb  | CorsParams:      null

but when i try to connect i get this:

my-dynamodb  | May 11, 2023 2:41:59 PM com.almworks.sqlite4java.Internal log
my-dynamodb  | WARNING: [sqlite] cannot open DB[1]: com.almworks.sqlite4java.SQLiteException: [14] unable to open database file
my-dynamodb  | May 11, 2023 2:41:59 PM com.almworks.sqlite4java.Internal log
my-dynamodb  | SEVERE: [sqlite] SQLiteQueue[shared-local-instance.db]: error running job queue
my-dynamodb  | com.almworks.sqlite4java.SQLiteException: [14] unable to open database file

it seems that the DB is not getting created in the

my-dynamodb-data

directory.

Hi, I installed rancher desktop in windows and pull one of my company image which is almost 6gb. it's starting the container but immediately exiting. Any help will be appreciated.

Hello, new to rancher. I installed rancher desktop on mac m1 pro. And when I run

k logs xxx

,I get

Error from server: Get "<https://192.168.5.15:10250/containerLogs/default/nginx-deployment-57d84f57dc-f7r9l/nginx>": EOF

. The problem is my IP is 10.100.x.x, not starts with 192. Would anyone help me?

Hello, Getting this error while pulling the image Error response from daemon: Get "https://orgURL/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers). Any help is apreciated.

Having a issue with newly created cluser stuck updating. The following messages is displyed on Rancher Gui Updating 1st-cluster Custom RKE2 v1.25.9+rke2r1 — — — Configuring bootstrap node(s) custom-a6b945c6f164: waiting for agent to check in and apply initial plan. Anyone ever run into this issue?

Hello, where are the k3s server manifests located on Rancher Desktop installed on Windows? I would like to disable local-path storage. Thanks

@fast-garage-66093 is https://github.com/rancher-sandbox/rancher-desktop/issues/2807 resolved?

Is there a ticket for this behavior? (New mac that doesn't have

/etc/sudoers.d

)

Error: Command failed: /bin/sh -xec 'cp "/var/folders/b_/d_v0syk90xvgp_8djqd14ct40000gn/T/rd-sudoers42398057.txt" /private/etc/sudoers.d/zzzzz-rancher-desktop-lima && rm -f "/var/folders/b_/d_v0syk90xvgp_8djqd14ct40000gn/T/rd-sudoers42398057.txt"'
+ cp /var/folders/b_/d_v0syk90xvgp_8djqd14ct40000gn/T/rd-sudoers42398057.txt /private/etc/sudoers.d/zzzzz-rancher-desktop-lima
cp: /private/etc/sudoers.d/zzzzz-rancher-desktop-lima: No such file or directory

When using the experimental networking tunnel, I'm experiencing issues doing DNS over tcp (when UDP response > 512) it times out calling the host (192.168.127.1) on port 53 over TCP. I'm wondering if the networking tunnel needs a configuration to forward tcp traffic over port 53 as well as UDP?