Hello, I need your help guys. I am using the latest stable Rancher version and trying to deploy an EKS cluster with custom AMI. When i deploy a node group without passing a custom AMI (using default one), everything is perfect and working. Cluster is healthy and rancher marks it as healthy. When i try to create a new node group with custom AMI (small modifications of ubuntu EKS AMI to meet my needs) without passing user-data, the node group creation fails because nodes cannot register to the cluster. If i pass user-data with bootstrap.sh then the nodes are registered to the cluster and node group is created correctly but then Rancher complains that it cannot find the rancher agent and doesn't show the cluster as healthy in the UI. What is the correct way to use Custom AMI with EKS downstream cluster and have Rancher agent installed on the nodes?

Hello Team . I am not able to open containers or images in Rancher Desktop. Getting Kubernetes Error . Have tried uninstalling and installing different version.

2025-07-24T11:43:40.389Z: Registered distributions: Debian,rancher-desktop-data,rancher-desktop,DWSL
2025-07-24T11:43:40.629Z: Registered distributions: Debian,rancher-desktop-data,rancher-desktop,DWSL
2025-07-24T11:43:40.839Z: Registered distributions: Debian,rancher-desktop-data,rancher-desktop,DWSL
2025-07-24T11:43:41.024Z: Registered distributions: Debian,rancher-desktop-data,rancher-desktop,DWSL
2025-07-24T11:43:41.024Z: data distro already registered

Hello Team , Its been long time , i am trying to create a workspace again as i was not able to use amazon workspace . its taking too long .

2025-07-29T06:09:09.055Z: Did not find a valid mount, mounting /mnt/wsl/rancher-desktop/run/data
2025-07-29T06:09:18.372Z: WSL: executing: cat /root/.docker/config.json: Error: wsl.exe exited with code 1

2025-07-29T06:09:18.702Z: WSL: executing: busybox readlink -f /etc/docker/daemon.json: Error: wsl.exe exited with code 1

may i check if any advise only how to resolve the this particular issue? i have tried deleted rancher folder and did clean installation but seems not working.

hello, can any one help me with this. i am using rancher to setup aws eks cluster. it was working but now giving [Disconnected] Cluster agent is not connected. in rancher.

hello here our project (Sylva project) relies on rancher-cis-benchmark chart that until yesterday was published in the charts.rancher.io Helm repository it stopped being published last night not only one version: this chart is totally absent from https://charts.rancher.io/index.yaml it seems possibly related to https://github.com/rancher/charts/pull/5856, which removed this chart -- but that PR was onyl supposed to remove it for the 2.12 series only would somebody know if this total removal of all versions of this chart was intended ?

hello @numerous-branch-51090 @cool-petabyte-32540 @few-plumber-96374 ... would you have any information on the question above on the disappearing of rancher-cis-benchmark chart ? ^^

I would like to give all rancher users access to the metrics graphics in the GUI. For this I assigned the global roles "User" and "View Rancher Metrics" to the "rancherusers" group (in FreeIPA). The rancherusers group is also a Cluster Member. Problem is, the colleagues logged in with their FreeIPA account still cannot see the metrics in Rancher, even though they are in the rancherusers group. The "Refresh Group Memberships" button doesn't help. Question is, how can I verify the FreeIPA integration wrt group search?

Hi.. I have a nexus running locally, where i store my images, to avoid hitting dockerhub limits with my rancher cluster. How to configure it with rancher? I want to deploy my images and pull it from my local nexus server.. i use HTTP as scheme.

i found this doc https://ranchermanager.docs.rancher.com/reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration#registries, but the linked document doesnt exist

Hello everyone, I currently have a downstream RKE2 cluster. I want to upgrade the cluster, but when I go to the Edit Config menu, the available RKE2 versions only go up to v1.31. I’ve tried upgrading the RKE2 version to v1.33 (which is not listed in Rancher) by manually editing the

kubernetesVersion

field in the YAML, and the upgrade was successful. Is that okay? I'm asking because Rancher itself only lists up to v1.31, and I used the RKE2 release from GitHub.

Hello Everyone, I installed a k3s single node cluster, some months ago, with traefik, letsencrypt, installed a mysql DB and 2 wordpress websites and one django website, this is just for some personal projects and learn some kubernets on the way. Everything was smooth but last week all websites were down, and today I start to investigate the problem, and it seems that my cluster is instable. Is seems that the k3s server is always restarting and I dont know where to start. So from my firts steps: • I have free memory, disk and CPU • Check the k3s version ◦ 1.31.5 • when i check the systemd status : ◦ Loaded: loaded (/etc/systemd/system/k3s.service; enabled; preset: enabled) ◦ Active: activating (start) since Thu 2025-07-31 183529 CEST; 1min 29s ago (this is always restarting) ◦ Docs: https://k3s.io ◦ Process: 14422 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service 2>/dev/null (code=exited, status=0/SUCCESS) ◦ Process: 14424 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS) ◦ Process: 14427 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS) ◦ Main PID: 14429 (k3s-server) ◦ Tasks: 441 ◦ Memory: 3.1G (peak: 5.1G) ◦ CPU: 2min 36.649s ◦ CGroup: /system.slice/k3s.service • And my journal logs: root@vmi2453314:~# journalctl -u k3s -xe Jul 31 183807 vmi2453314 k3s[14429]: I0731 183807.459437 14429 metrics.go:299] "Failed to get storage metrics" storage_cluster_id="etcd-0" err="context deadline exceeded" Jul 31 183820 vmi2453314 k3s[14429]: I0731 183820.463378 14429 metrics.go:299] "Failed to get storage metrics" storage_cluster_id="etcd-0" err="context deadline exceeded" Jul 31 183823 vmi2453314 k3s[14429]: time="2025-07-31T183823+02:00" level=info msg="Waiting for API server to become available to start kube-scheduler" Jul 31 183823 vmi2453314 k3s[14429]: time="2025-07-31T183823+02:00" level=info msg="Waiting for API server to become available to start cloud-controller-manager" Jul 31 183823 vmi2453314 k3s[14429]: time="2025-07-31T183823+02:00" level=info msg="Waiting for API server to become available" Jul 31 183825 vmi2453314 k3s[14429]: time="2025-07-31T183825+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.151450 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183825 vmi2453314 k3s[14429]: time="2025-07-31T183825+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.151432 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183825 vmi2453314 k3s[14429]: time="2025-07-31T183825+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.151416 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183825 vmi2453314 k3s[14429]: time="2025-07-31T183825+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.151434 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183825 vmi2453314 k3s[14429]: time="2025-07-31T183825+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.151466 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183825 vmi2453314 k3s[14429]: E0731 183825.487717 14429 remote_available_controller.go:448] "Unhandled Error" err="v1beta1.metrics.k8s.io failed with: failing or missing response from https://10.42.0.135:1025> Jul 31 183831 vmi2453314 k3s[14429]: I0731 183831.538689 14429 controller.go:615] quota admission added evaluator for: endpoints Jul 31 183833 vmi2453314 k3s[14429]: time="2025-07-31T183833+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.141060 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183833 vmi2453314 k3s[14429]: time="2025-07-31T183833+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.141044 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183833 vmi2453314 k3s[14429]: time="2025-07-31T183833+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.141032 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183833 vmi2453314 k3s[14429]: time="2025-07-31T183833+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.141030 dial tcp 10.42.0.13510250 connect: no route to host" Jul 31 183833 vmi2453314 k3s[14429]: time="2025-07-31T183833+02:00" level=error msg="Sending HTTP/1.1 502 response to 127.0.0.141020 dial tcp 10.42.0.13510250 connect: no route to host"

Howdy !! Rancher v2.12 with K8s 1.33 and ARM support is released https://github.com/rancher/rancher/releases/tag/v2.12.0

Folks, I ran:

kubectl delete daemonset rke2-ingress-nginx-controller -n kube-system

It's gone and now I want to get the ingress-nginx-controller back and it's becoming tough. I thought applying

/var/lib/rancher/rke2/server/manifests/rke2-ingress-nginx.yaml

would help, but no. Re-starting

rke2-server

with the thought that it'll re-deploy it, doesn't work either. What can I try next?

Hi All, need some help. Using K3sContainer in java.

k3s:v1.31.11-k3s1

I deploy K3sContainer and some GenericContainer. both having same Network. GenericContainer is webapp .

new GenericContainer<>(MY_APP_IMAGE)
        .withExposedPorts(8089)
        .withNetwork(network)
        .withNetworkAliases("myapp");

if i try to:

wget myapp:8089

from k3s to myApp - works. But if I deploy a pod in k3s, and from that pod try the same, i get: Could not resolve host: myapp if I take the actual IP and use it instead, all works. but i need to use the name.

Hello there, I follow this procedure for restoring a backup with Rancher backup: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher I use S3 Bucket like it is explained on a fresh k3s/Rancher install on which only Rancher backup is added Versions of k3s (v1.32.6+k3s1), Rancher (2.11.3) and Rancher Backup (v106.0.2+up7.0.1) are the same as the original deployment But when the restore start after a while, an error occured with projects that cannot be deleted because they are system projects in local namespace. And the process loops endlessly Not a problem, I stop the restore by deleting the file in the bucket, Rancher restarts correctly I delete projects manually, easy I restart a restore, but now I have webhook call errors. But it seems to be normal because the rancher-operator scales down the rancher deployment during restore, like it is explained in the documentation So I don't undestand something some help would be appreciated, thank you

Hi, I get the following error while registering a node to a newly created cluster

time="2025-08-04T10:42:07Z" level=info msg="Waiting for node to register. Either cluster is not ready for registering, cluster is currently provisioning, or etcd, controlplane and worker node have to be registered"
 time="2025-08-04T10:42:09Z" level=info msg="Waiting for node to register. Either cluster is not ready for registering, cluster is currently provisioning, or etcd, controlplane and worker node have to be registered"
 time="2025-08-04T10:42:10Z" level=debug msg="Wrote ping"
 time="2025-08-04T10:42:11Z" level=info msg="Waiting for node to register. Either cluster is not ready for registering, cluster is currently provisioning, or etcd, controlplane and worker node have to be registered"

👋 Hi everyone!

I just installed Rancher Desktop (version 1.19.3) , I have a failing pod on the k8s clusters. the kube-image/builder is failing with

error while dialing: dial unix /run/buildkit/buildkitd.sock: connect: no such file or directory

. I running RD with moby.

Hello rancher teams, I have a question. When I check the Account and API Keys page, I see that there are many kubeconfigs that have been generated previously. My question is: why do some kubeconfigs show a "Scope" while others display a dash (-) instead? What causes the "Scope" to appear as a dash when generating a kubeconfig? I would like each kubeconfig to include its Scope so that I can easily identify which cluster it belongs to. Is there a way to configure or set this behavior?

Rancher Desktop is stuck at one stage, showing no containers. Reinstalling Rancher Desktop and WSL, and unregistering Ubuntu didn't help. Suspects proxy or VPN blocking it, as it works on others' machines. Needs it to run API code locally.

Hello everyone, I hope someone can help me understand the problem: I just installed Rancher and am trying to connect my GKE cluster, but I am getting this error:

Get "<https://container.googleapis.com/v1/projects/s24-prj-dev-it-gke-01/locations/europe-west8/clusters/s24-gke-ew8-dev-it-cluster-01?alt=json&prettyPrint=false>": oauth2: cannot fetch token: Post "<https://oauth2.googleapis.com/token>": dial tcp: lookup <http://oauth2.googleapis.com|oauth2.googleapis.com> on 10.43.0.10:53: server misbehaving

Has anyone else encountered this issue? Many thanks in advance to anyone who can help me.

Hi! What is the process for getting new calico images added to the rancher mirror? https://github.com/rancher/image-mirror/issues/1054. I'd love to help or get the MR's put together, but don't want to step on toes if there is an existing process that someone is already running

Hey all, I am trying to run istio in k3s and have no use of traefik. I tried running k3s with

--disable=traefik

but running this also removes serviceLB which I require. Is there a way I can install serviceLB without traefik Thanks

~Rancher Desktop 1.19.3 , MacOS 15.6 rdctl gives the below error~

Hi, we are running rancher on a single node docker install and we frequently run into this error:

2025/08/06 143013 [FATAL] Internal error occurred: failed calling webhook "rancher.cattle.io.settings.management.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/validation/settings.management.cattle.io?timeout=10s": no endpoints available for service "rancher-webhook"

We can get around it by following the instructions here: https://github.com/rancher/rancher/issues/35068#issuecomment-954457381 We are on rancher version v2.11.1 but this has happened since v2.8.5. One thing to note is that we do stop the rancher docker container frequently for backups by following the instructions in Backing up Rancher Installed with Docker Any ideas how to prevent this from happening?

Hi All, has anyone of you succeeded in configuring Rancher to add a GKE cluster?

Hey all, I am trying to achieve this, I have an application running which needs to connect to an external service which only accepts whitelisted ips. I want to configure my cluster or application to egress or make every outbound request from this whitelisted IP (a node in the cluster has this ip).

Asking here as I cant see a more appropriate channel (please point one out?) I was hoping to add Rancher metrics (downstresam cluster availability among others) to prometheus. I have found https://github.com/David-VTUK/prometheus-rancher-exporter however it appears no longer supported. Are there any other endpoints available to scrape to get a view of Rancher and friends in Prometheus?

Hi, I have recenetly installed Rancher Desktop, earlier i was using Docker Desktop - in which i was trying to access Network DB using VPN which was able to connect successfully. While in Rancher that VPN DB is not reachable. If anyone can help here that would be greatful. I have tried couple solution but haven't succeeded yet. Let me know if any further details are needed.