Is it possible to run Rancher 2.6.6 in Docker 20.10.17 on Ubuntu 22.04 without making a cgroup2 mod as follows:

GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"

Hey Guys I need some help, I am trying to install Rancher per and a video I watched on a VM by itself so I can build 2 kubernetes clusters with K3s, However I keep getting this error (os Ubuntu Server 18.04.6, Rancher is Latest): "FATA[0000] cluster and rancher are not ready. Please try later.: the server could not find the requested resource" Any ideas where can I look for the logs so I can try and get this resolved. Thanks

Hi folks. I've been struggling trying to add an agent node to K3s cluster, seeing the following in journal when starting k3s-agent daemon:

Aug 16 20:56:25 ip-xx-xx-xx-xx.us-east-2.compute.internal k3s[4056]: W0816 20:56:25.659366    4056 reflector.go:324] <http://k8s.io/client-go@v1.24.3-k3s1/tools/cache/reflector.go:167|k8s.io/client-go@v1.24.3-k3s1/tools/cache/reflector.go:167>: failed to list *v1.Endpoints: Get "<https://127.0.0.1:6444/api/v1/namespaces/default/endpoints?fieldSelector=metadata.name%3Dkubernetes&limit=500&resourceVersion=0>": net/http: TLS handshake timeout

Any ideas on what to try would be greatly appreciated.

regarding K3s, if i want to add a new agent located in WAN/Cloud, while master and other workers are on LAN, which flag should I be using to ensure new workers use the correct Hostname/IP. I had hoped to be able to specify the location of the K3s Server at the agent config side, but this doesn't seem to be the case? I have a dynamic DNS record configured to point to a resolvable IP/Port combination. I tried setting the "advertise-address" or node external IP values, but I still see see:

Aug 16 18:12:49 Kube-0 k3s[3070]: I0816 18:12:49.519375    3070 server.go:576] external host was not specified, using 192.168.0.83

In journal conf:

kubes@Kube-0:/etc/rancher/k3s$ cat config.yaml
write-kubeconfig-mode: 644
token: "<removed>"
advertise-address: <https://conallogribin.dyns.cx:6443>
node-external-ip: <https://conallogribin.dyns.cx:6443>

Does anyone have any experience getting airflow up on a rancher cluster? It mostly seems to work but gives an error about mounting my NFS storage. I can confirm that the mount does work otherwise.

Has anybody was able to mount docker images and work with AWS Lambda locally using Rancher Desktop and AWS SAM?

Hi, am trying to create new EKS cluster from Rancher GUI. Am not able to skip Node Group details ? Version of Rancher is 2.6.5. If I choose node group, what should I fill in UserData?. When I try as is, it fails on nodegroup join error

Hello , i updated rancher running in k3s cluster using helm upgrade to the new version , rancher is working well all clusters are in rancher server but when i am trying to connect to the cluster using Kubeconfig from rancher it is returning this error :

"2022/08/17 07:59:25 [ERROR] Failed to handling tunnel request from remote address  response 400: cluster not found
2022/08/17 07:59:26 [ERROR] Failed to handling tunnel request from remote address  response 400: cluster not found
2022/08/17 07:59:26 [ERROR] Failed to handling tunnel request from remote address  response 400: cluster not found
2022/08/17 07:59:27 [ERROR] Failed to handling tunnel request from remote address  response 400: cluster not found
2022/08/17 07:59:28 [ERROR] Failed to handling tunnel request from remote address  response 400: cluster not found
2022/08/17 07:59:29 [ERROR] Failed to handling tunnel request from remote address  response 400: cluster not found
2022/08/17 07:59:30 [ERROR] Failed to handling tunnel request from remote address  response 400: cluster not found
2022/08/17 07:59:32 [ERROR] Failed to handling tunnel request from remote address : response 400: cluster not found
2022/08/17 07:59:32 [ERROR] Failed to handling tunnel request from remote address  response 400: cluster not found"

Does anyone have experience with Rancher EC2 SPOT instances?

Why doesn't Rancher have an IPAM solution or allow you to use an IPAM solution for addressing control plane / worker nodes?

Also is there a way to add an already created Linux server into a cluster?

Hey, How is the

~/.rd/docker.sock

created? I’m trying to understand how Rancher works internally, but can’t figure out how is the socket for the docker communication created.

I'm having a hard time getting Longhorn to work. I've installed open-scsi and nfs-utils, then installed Longhorn using helm and created a PVC. When trying to start a container with mounted PV, it stays in ContainerCreating then moves to Terminating. There's almost no relevant logs that I can find anywhere except for this from the terminating conatiner:

Warning  FailedAttachVolume  30s (x3 over 34s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-59d0a314-528d-4477-9556-118d2e7bf756" :
 rpc error: code = DeadlineExceeded desc = volume pvc-59d0a314-528d-4477-9556-118d2e7bf756 failed to attach to node ip-10-0-126-227.us-east-2.compute.internal

I checked that both

iscsid

and

nfs-utils

services are active.

I am using github sso in rancher. we are not able to add github teams as cluster member.while adding we are getting all the public github groups in list but not the private groups associated with organisation.

Is there a way to prevent users from creating unscoped API tokens?

Has anyone gotten Rancher 2.6.6 to run in podman? I managed to fix an issue with uid mapping, but k3s is crashing on startup in the same way that it does in docker on a cgroup v2-enabled system. I had read that podman does not have the cgroup v2-based issues, so thought I’d try to get it running there.

Hello Rancher! I am trying to get pricing information, filled out the contact page twice, but got no confirmation on-screen or via e-mail. Rancher website also lists no e-mail address. Does anyone have an email address I can use to contact Rancher?

2022/08/12 20:13:50 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=Amazonec2MachineTemplate 2022/08/12 20:13:50 [INFO] Watching metadata for management.cattle.io/v3, Kind=Node 2022/08/12 20:13:50 [INFO] Watching metadata for apps/v1, Kind=StatefulSet 2022/08/12 20:13:53 [INFO] Adding peer wss://192.68.101.82/v3/connect, 192.68.101.82 2022/08/12 20:13:53 [ERROR] Failed to connect to peer wss://192.68.101.82/v3/connect [local ID=192.68.102.155]: websocket: bad handshake 2022/08/12 20:38:03 [ERROR] Error during subscribe websocket: close sent 2022/08/12 20:38:03 [ERROR] Error during subscribe websocket: close sent Is anyone faced this kind of websocket close connection in rancher containers ?

#rancher-desktop Getting error "404 page not found" for http://localhost/ after installing rancher desktop

could any one help on this?

facing this issue in windows

Hi All. Is it possible to change the K3S_TOKEN of your cluster, without re-installing the cluster?

👋 Hi everyone! Hope anyone can help or had a similar experience wrt Rancher. We deleted one node because we had some issues with it. After deleting the node Rancher started provisioning many new nodes and keeps deleting them right after. It's stuck in a loop somehow spamming our infrastructure. What could be causing this? This is happening on EC2 and seems like this issue. We are on rancher 2.6.6.

is there procedure how to upgrade rancher running in HHA on gke?

Hi all! I am creating downstream a RKE cluster using the Terraform rancher2 provider with nodes having private IP addresses only, using virtual network peering to connect the Rancher management cluster and downstream RKE vnets. Without using a load balancer all nodes are registered successfully but when I want to create the cluster with an addon deployment job for external ingress load balancer, some worker nodes are stuck indefinitely in "Registering state". The provisioning log for the cluster completes successfully and all pods in all namespaces are running and jobs completed. I was able to access the stuck nodes and look at the rancher-agent logs:

INFO: Arguments: --no-register --only-write-certs --node-name system1 --server <https://rancher.sauron.mordor.net> --token REDACTED --ca-checksum 928a476fa0b0610ef46217292d51ac438f4ffa56ea3b155f240ee89ff4c1f31b

INFO: Environment: CATTLE_ADDRESS=10.100.0.4 CATTLE_AGENT_CONNECT=mordor CATTLE_INTERNAL_ADDRESS= CATTLE_NODE_NAME=system1 CATTLE_SERVER=<https://rancher.sauron.kangaroot.net> CATTLE_TOKEN=REDACTED CATTLE_WRITE_CERT_ONLY=true

INFO: Using resolv.conf: nameserver 127.0.0.53 options edns0 search <http://u52yollp52yetgbxgli0ra2ssb.ax.internal.cloudapp.net|u52yollp52yetgbxgli0ra2ssb.ax.internal.cloudapp.net>
WARN: Loopback address found in /etc/resolv.conf, please refer to the documentation how to configure your cluster to resolve DNS properly
ERROR: <https://rancher.sauron.mordor.net/ping> is not accessible (Failed to connect to <http://rancher.sauron.mordor.net|rancher.sauron.mordor.net> port 443: Connection timed out)

Any idea ? I would greatly appreciate help on this! I opened an issue with the code used and provisioning log for the cluster: https://github.com/rancher/terraform-provider-rancher2/issues/972```

Also, it would be nice to have the ability to edit sent messages without a limit of time 🙂

@fast-piano-59234 @full-painter-23916 I am pinging you two because you have had good answers for me in the past. I am experiencing the same issue as outlined in this issue on github. https://github.com/rancher/rancher/issues/21324. However that issue has been open since 2019 with no resolution. Basically what happens is that I run this command:

rancher kubectl rollout status -w deployment acmepa -n acmepa

It immediately replys with

deployment "acmepa" successfully rolled out

but then hangs there for 5 minutes or so.

Having an issue with the Harvester Install from PXE. The install goes pretty far but stalls on Checking 33 images in /var/lib/rke2/agent/images/harvester-images-v1.0.2.txt... I can't find out what it is doing and where to see the progress if it is actually getting images but taking it's sweet time. Any Help?

Hi,