I am new with Rancher Desktop

I just install on MAC system but when I am trying to execute docker-compose it [+] Building 0.0s (0/0) no valid drivers found: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Is there anything i need to execute?

--> #rancher-desktop

Hi everyone, on one Rancher installation I find the SAML SP metadata at /v1-saml/shibboleth/saml/metadata working, but on a new one it returns 404. I couldn't find anything changed in the documentation. Any ideas?

I have deployed rancher server on a VM i am trying to add git repository in continuous delivery but it fails (Could not resolve hostname)

nvm, i see it, it is in another section call “cluster management” Sorry

hi y'all! I'm getting this error message, mostly when trying to interact with existing cluster through terraform, and also when opening one particular URL in the browser: ```

Hey all! I'm new here and noob to the clusters stuff. I followed this document to install rancher on K3s: https://docs.rancherdesktop.io/how-to-guides/rancher-on-rancher-desktop/ Everything works perfect but after I restart my pc and launch rancher desktop I see K3s up in kubectl. But also I see no containers running image in "nerdctl ps" output including the rancher one. So I can't login back using the password I setup. If I run new rancher container with the instruction from docs: nerdctl run --privileged -d --restart=no -p 8080:80 -p 8443:443 rancher/rancher It prompts me for the Bootstrap Password and setting the user password again. What should I do to preserve the user passwrord from the first setup and use it across the reboots?

Hi

Where are the Repositories listed under a cluster's Apps synced to? into a pod on the cluster, the rancher server or where? I have an issue that all repos are in a "In Progress" state and no charts show up. deleting and readding the repos doesn't change anything. This is 2.7 and I have this issue with only one cluster.

In version 2.7.0, is there any way to turn of the validatingwebhookconfiguration and mutatingwebhookconfigurations for *.cluster.x-k8s.io. I am running the Kubernetes Cluster API on my Rancher cluster and the webhook configurations and conflicting causing some weird errors when changing objects or interacting with the Cluster API items. I have deleted the configurations a few times but they keep coming back.

when I run

kubectl get nodes

, the node's status is shown as

Ready

, so I am confused

Guys, I have a simple question. The Rancher (or Suse), have active RSS Feed to notify about new releases, issues or corrections? I want to integrate this Feed on my slack to receite notifications and prevent problems on the Rancher product

Hi, i'm running a rancher 2.6.9 ha setup and suddenly the rancher pods started crashing i am seeing the following in the pods logs: k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x0?, 0x3b9aca00, 0x0, 0x0?, 0x0?) /go/pkg/mod/k8s.io/apimachinery@v0.24.2/pkg/util/wait/wait.go:133 +0x89 k8s.io/apimachinery/pkg/util/wait.Until(0x0?, 0x0?, 0x0?) /go/pkg/mod/k8s.io/apimachinery@v0.24.2/pkg/util/wait/wait.go:90 +0x25 created by github.com/rancher/lasso/pkg/controller.(*controller).run /go/pkg/mod/github.com/rancher/lasso@v0.0.0-20220628160937-749b3397db38/pkg/controller/controller.go:148 +0x2a7 panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x80 pc=0x2c17de6] goroutine 99177 [running]: k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc0166784b0?}) /go/pkg/mod/k8s.io/apimachinery@v0.24.2/pkg/util/runtime/runtime.go:56 +0xd7 panic({0x38a9be0, 0x6f29d10})

Disk pressure issue on node running rancher.

👋 Hi everyone! Any experience with Monitoring chart not working on v2.7.0? It seems that pushprox-k3s-server-client is using alpine 3.13.5, for which DNS options ndots:5 could be faulty. (That's my closest guess as far as I understand it yet) The symptoms are - monitoring in Grafana just can't display information about other nodes than the Master node of the cluster. And digging into it, apparently the pushprox-k3s-server-client just cannot resolve service names.

Hi Ranchers , I installed ingress controller in rancher desktop in my windows box. The ingress controller IPs seems to change in every reboot. Is there way to fix it ? Thanks

Hi , i'm trying to run rancher dashboard to show my k8s clusters but it stuck on loading

mac os m1

any idea?

Hi Ranchers , i'm trying to implement longhorn csi with rancher cluster the case is that i have an encrypted disk with luks already, the provisioned volumes are faulted, once i have removed luks from disk every this came to healthy and i also found that longhorn can encrypt volumes by it self so is the encrypted disk don't work with longhorn and if i need encryption use longhorn encryption, please support ??

A customer approached me about the difference between rke1 and rke2 from a support prespective. does rancher treat both product lines the same? Will they provide long term support for rke1 ?

Any clear explanation or recommendation to preffer rke2 vs rke1 or vice versa?

Hi all, I’ve a cluster using k3s on raspberryPis. This cluster works perfectly for almost a year, and a few hours when I try to get any data from the cluster using kubectl I receive

You must be logged in to the server (Unauthorized)

Checking the master node, the k3s service Im seeing this:

● k3s.service - Lightweight Kubernetes
     Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-01-09 00:57:40 GMT; 26s ago
       Docs: <https://k3s.io>
    Process: 29663 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service (code=exited, status=0/SUCCESS)
    Process: 29665 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
    Process: 29666 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
   Main PID: 29667 (k3s-server)
      Tasks: 105
     Memory: 713.5M
        CPU: 55.998s
     CGroup: /system.slice/k3s.service
             ├─27643 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id 866ca3db8ed3>
             ├─27988 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id 699af3f5d3c1>
             ├─28196 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id ac9ec12775e6>
             ├─28317 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id b345387839df>
             ├─28535 /var/lib/rancher/k3s/data/73e12683e3eb1c52a6370763bda6bb977c304a3b6cda6e5c7656f45f3725e7dd/bin/containerd-shim-runc-v2 -namespace <http://k8s.io|k8s.io> -id 880445942eb9>
             ├─29667 /usr/local/bin/k3s server
             └─29683 containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/ra>

Jan 09 00:58:01 facio k3s[29667]: I0109 00:58:01.010177   29667 ttl_controller.go:121] Starting TTL controller
Jan 09 00:58:01 facio k3s[29667]: I0109 00:58:01.010203   29667 shared_informer.go:240] Waiting for caches to sync for TTL
Jan 09 00:58:01 facio k3s[29667]: I0109 00:58:01.022756   29667 node_ipam_controller.go:91] Sending events to api server.
Jan 09 00:58:01 facio k3s[29667]: E0109 00:58:01.441328   29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>
Jan 09 00:58:04 facio k3s[29667]: E0109 00:58:04.547721   29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>
Jan 09 00:58:04 facio k3s[29667]: E0109 00:58:04.548614   29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>
Jan 09 00:58:04 facio k3s[29667]: E0109 00:58:04.548867   29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>

I saw this error before but I reinstall the cluster. I prefer not to do it again to avoid loosing data. Anyone knows how I can fix:

"Unable to authenticate the request" err="[x509: certificate has expired or is not yet v>

(edited) [1:09 AM] I havent changed anything on the machine running K3S at all

checking journalctl shows this:

Jan 09 01:18:01 facio k3s[29667]: E0109 01:18:01.542615   29667 authentication.go:63] "Unable to authenticate the request" err="[x509: certificate has expired or is not yet valid: current time 2023-01-09T01:18:01Z is after 2023-01-08T22:37:57Z, verifying certificate SN=2555825581207100645, SKID=,AKID=8F:E9:C8:2E:7F:91:B7:01:BC:7A:48:DD:77:8C:6A:EF:92:DA:E5:58 failed: x509: certificate has expired or is not yet valid: current time 2023-01-09T01:18:01Z is after 2023-01-08T22:37:57Z]"

can’t understand how this happened

current time 2023-01-09T01:18:01Z is after 2023-01-08T22:37:57Z

I’ve just installed rancher-desktop for the first time on macos, and on the command line, I don’t seem to be able to list images in the registry - I can’t even pull a specific image from the docker registry. This is the error message I get:

> nerdctl pull alpine
INFO[0000] trying next host                              error="failed to do request: Head \"<https://registry-1.docker.io/v2/library/alpine/manifests/latest>\": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused" host=<http://registry-1.docker.io|registry-1.docker.io>
ERRO[0000] server "<http://docker.io|docker.io>" does not seem to support HTTPS  error="failed to resolve reference \"<http://docker.io/library/alpine:latest\|docker.io/library/alpine:latest\>": failed to do request: Head \"<https://registry-1.docker.io/v2/library/alpine/manifests/latest>\": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused"
INFO[0000] Hint: you may want to try --insecure-registry to allow plain HTTP (if you are in a trusted network)
FATA[0000] failed to resolve reference "<http://docker.io/library/alpine:latest|docker.io/library/alpine:latest>": failed to do request: Head "<https://registry-1.docker.io/v2/library/alpine/manifests/latest>": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused
Error: exit status 1

(If there’s a more appropriate channel, please let me know! 😬 )

Hey there ! ICYMI - the Longhorn team release v1.4 just before the new year. If you want a quick run through of what some of the enhancements are - check out this blog https://www.suse.com/c/rancher_blog/longhorn-1-4-starting-a-new-year-with-a-new-release/ Posted in #longhorn-storage

hello folks I am new to Rancher and I want to build my small data center using rancher but I also want to share my gpu to VM so it is possible using rancher os thank you