Not sure if this is possible or not.

I cannot run single node rancher on mac M1. i tried with podman and I got

INFO: Running k3s server --cluster-init --cluster-reset
2022/11/17 03:17:56 [INFO] Rancher version c0f6cdb9a (c0f6cdb9a) is starting
2022/11/17 03:17:56 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2022/11/17 03:17:56 [INFO] Listening on /tmp/log.sock
2022/11/17 03:17:56 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/11/17 03:17:58 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/11/17 03:18:00 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/11/17 03:18:02 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/11/17 03:18:04 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/11/17 03:18:05 [FATAL] k3s exited with: exit status 1

@creamy-pencil-82913

I could not execute shell on any container in K8S(v1.23.7+rke2r2). Any help will be very pleasure. 🙂https://github.com/rancher/rancher/issues/39635

I'm struggling to set up Rancher desktop on Windows behind a corporate Proxy which requires authentication. Currently, k3s Bootstrapping fails with

Fetching releases from <https://api.github.com/repos/k3s-io/k3s/releases?per_page=100> -> AuthorizedOnly

I figured out a way to establish connectivity on other WSL distros: On the windows host, there is a local Proxy server running on port 8887, and I have a shell script which determines the right Network Interface and IP Addresses and sets the variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY accordingly to route all traffic from the wsl guest machine through this local proxy server which cares for Authentication. This works fine with and without VPN in our corporate network and from remote work locations. Now, I would like to: *let Rancher Desktop (Windows executables) point to localhost:8887 as proxy Server *let Rancher WSL Distros set HTTPS_PROXY, HTTP_PROXY, NO_PROXY via that shell script which picks the right network interface to determine the current IP Address How could this be achieved?

Hi, I'm trying to figure out how to attach fewer labels to timeseries stored by prometheus as described in https://docs.ranchermanager.rancher.io/how-to-guides/advanced-user-guides/monitoring-alerting-guides/debug-high-memory-usage#reducing-memory-bursts. Is there a way to exclude labels when using the helm chart for the rancher monitoring stack (grafana/prometheus/alertmanager)?

Hello all, I have setup a k3s cluster on AWS EC2 instances (one master + 2 worker nodes). I am trying to deploy a pod on one of the worker nodes, in this pod a docker image is pulled and this docker image internally is running some scripts to fetch package from the internet. But I am seeing an issue with DNS resolution in this pod

wget: unable to resolve host address

however upon logging onto that pod and trying to ping 8.8.8.8, the packets are being transmitted successfully.

bash-4.3# ping <http://google.com|google.com>
ping: bad address '<http://google.com|google.com>'

bash-4.3# 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=49 time=1.133 ms
64 bytes from 8.8.8.8: seq=1 ttl=49 time=1.084 ms
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.083/1.109/1.137 ms
bash-4.3#

Note: 1. Security groups are proper with access to all http traffic. So I am not sure why the DNS resolution is failing on the EC2 instances. I have tried restarting coredns service

sudo kubectl -n kube-system rollout restart deployment coredns

and it temporarily fixes the issue but when I delete and recreate the pod, I again see issue with DNS resolution. Please let me know of there is anything needs to be changed in config files or is there any setup issue.

Hi Lads, was someone able to succesfuly deploy k8s cluster using rancher 2.6.9 , rke2 and vsphere. I’m nearly there but ui displays that it stucked on “Updating”. “Non-ready bootstrap machine(s) test-node-selectors-pool1-644585c7ff-qgrtx and join url to be available on bootstrap node” Thanks for any help

Hi, does anyone know how to debug this error when provisioning a new cluster?

2022/11/17 22:09:38 [ERROR] cluster [c-jpmvb] provisioning: [[network] Host [10.10.50.53] is not able to connect to the following ports: [10.10.50.44:2379]. Please check network policies and firewall rules]

https://github.com/rancher/rancher/issues/14249#issuecomment-1319249541

The control node can telnet to the

etcd

node on port 22 but not on port 2379, yet I can

telnet 10.10.50.44 2379

from the

etcd

node itself (

10.10.50.44

)

Hi, does anybody know why the rancher installation with external tls via the rancher docs on a k3s cluster also setup via the docs does not open the webserver on port 80 like it says in the docs? The docs talks about nginx but i only see traefik in my cluster. I followed these tutorials: https://docs.ranchermanager.rancher.io/v2.5/how-to-guides/new-user-guides/kubernetes-cluster-setup/k3s-for-rancher https://docs.ranchermanager.rancher.io/pages-for-subheaders/install-upgrade-on-a-kubernetes-cluster My helm command:

helm install rancher rancher-latest/rancher \
  --namespace cattle-system \
  --replicas=3 \
  --set hostname=<http://mydomain.com|mydomain.com> \
  --set tls=external

If been trying to figure this out for weeks 😞

hi, I’m able to expose a clusterIp to map a localhost port with

k3d cluster create --api-port 6550 -p "8081:80@loadbalancer" --agents 3

but how can I have multiple port mapping to use ingress to handle multiple k8s services/apps? I would like to do something like

k3d cluster create --api-port 6550 -p "7001-7001:8081-80@loadbalancer" --agents 3

is that possible?

Rancher server is redirecting to https even though i have set tls=external when doing a helm install. I went in to the pod and curl ed the localhost and still getting redirected. How do i fix this ?

Does anyone know the k8s version range that rancher 2.7.0 supports? I typically look here but it hasn't been updated yet 😄

God Morning, is there any way of controlling the options of user API keys? Like disable having the setting “never” as expiry and perhaps set 8hrs as default.

Hi, It is possible for grafana dashboard to display the hostname instead of IP and port when using rancher monitoring.The helm chart used is rancher-monitoring 100.1.3+up19.0.3.The rancher version is 2.6.9 and k8s version is 1.23.10 installed using rke.

I have a question about the Rancher cluster itself. Would it be possible to spread the cluster over multiple environments? We have our on-prem production datacentre, a DR centre and presence in Azure via an Express Route whith <20ms latency to production (can't remember if 5ms or 12ms, will check with networks team). Would it be possible to spread Rancher's local cluster across these points, to allow it to remain active, if any one of them should experience an issue? Or am I whistling Dixie through parts unmentioned? Edit: layout

I am using rancher desktop in a windows virtual machine so i want to know where the rancher desktop store images build by it

Hi folks, someone could give me an idea why could I get my k3s HA cluster fail to join:

The error I saw is this: ETCD join failed: etcdserver: too many learner members in cluster

Hello All, My cluster details are: • Rancher 2.5.8 • RKE 1.2.13 • Upstream HA cluster Issue: • Suddenly Rancher UI stopped working • UI Error: 503 Service Temporarily Unavailable What can be the issue and how to check it? Please guide. I have also lost my KUBECONFIG file, how can I restore/retrieve it?

Hi all, one silly question, can i update my cluster ETCD backup s3 after creating cluster and application is deployed. because. I see some settings are not correct.

Hi I'm trying to use

kubectl

with a downstream cluster. I have fetched the kubeconfig with rancher cli:

rancher clusters kubeconfig CLUSTER-ID CLUSTER-NAME > kubeconfig

kubectl

commands fail with

Unable to connect to the server: x509: certificate signed by unknown authority

where should I look into to find the problem? which certificate is it talking about? is this related to the contents of

clusters.*.cluster.certificate-authority-data

in the kubeconfig file?

has anyone gotten rke to work on ubuntu 22.04

I am seeing two issues: (1) ingress webhook error and (2) no LoadBalancer and NodePort services are inaccessible outside of k8s cluster nodes

I don't know if this is an rke thing or Kubernetes in general

👋 Hi everyone!

Im trying to spin up a docker container in rancher os and im facing as error as java or JRE_HOME is not available. I relatively new to this. Any pointers on how i can resolve this ?

This is currenly hosted on digital ocean cloud

Logs:

[rancher@bb-rancheros ~]$ docker volume create --name bitbucketVolume

bitbucketVolume

[rancher@bb-rancheros ~]$ docker run -v bitbucketVolume:/var/atlassian/application-data/bitbucket -p 7990:7990 -p 7999:7999 atlassian/bitbucket

WARNING:root:######################################################################

WARNING:root:Starting Bitbucket with embedded search service. Note that this is

not a recommended configuration and is known to have issues with

clean shutdown. Ideally OpenSearch (previously Elasticsearch) should

be started in a separate container/pod.

WARNING:root:######################################################################

INFO:root:User is currently root. Will downgrade run user to bitbucket

INFO:root:Running Bitbucket with command '/opt/atlassian/bitbucket/bin/start-bitbucket.sh', arguments ['/opt/atlassian/bitbucket/bin/start-bitbucket.sh', '-fg']

The JRE_HOME environment variable is not defined correctly

This environment variable is needed to run this program

Edit set-jre-home.sh and define JRE_HOME

Startup has been aborted

[rancher@bb-rancheros ~]$