big-pilot-12003
07/18/2024, 4:37 PMbland-article-62755
07/19/2024, 6:49 PMflat-tailor-24175
07/22/2024, 2:34 AMglamorous-umbrella-16701
07/22/2024, 3:15 AMgifted-plastic-62559
07/22/2024, 7:34 AMcrooked-cat-21365
07/22/2024, 7:55 AMboundless-animal-70300
07/22/2024, 3:35 PMgorgeous-judge-99858
07/22/2024, 3:43 PMlimited-pizza-33551
07/23/2024, 5:46 AMalert-horse-23341
07/23/2024, 8:15 AMrancher
locally and I am not able to make the latest docker hub image to start. Always getting the following error:
2024/07/23 08:07:18 [ERROR] error syncing 'rancher-partner-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-partner-charts/8f17acdce9bffd6e05a58a3798840e408c4ea71783381ecd2e9af30baad65974 fetch origin -- 5b498cba1c410428f26445b061a1a7a5741b9aa4 error: exit status 128, detail: fatal: unable to access '<https://git.rancher.io/partner-charts/>': Insufficient randomness
, handler helm-clusterrepo-download: update failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-partner-charts/8f17acdce9bffd6e05a58a3798840e408c4ea71783381ecd2e9af30baad65974 fetch origin -- main error: exit status 128, detail: fatal: unable to access '<https://git.rancher.io/partner-charts/>': Insufficient randomness
, requeuing
2024/07/23 08:07:21 [ERROR] error syncing 'library': handler catalog: Update failed: fatal: unable to access '<https://git.rancher.io/charts/>': Insufficient randomness
: exit status 128, requeuing
2024/07/23 08:07:37 [ERROR] error syncing 'system-library': handler catalog: Update failed: fatal: unable to access '<https://git.rancher.io/system-charts/>': Insufficient randomness
: exit status 128, requeuing
2024/07/23 08:07:43 [ERROR] error syncing 'rancher-rke2-charts': handler helm-clusterrepo-ensure: ensure failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-rke2-charts/675f1b63a0a83905972dcab2794479ed599a6f41b86cd6193d69472d0fa889c9 fetch origin -- ea1c4cd682e965230bf30a777c340a8fc3c12cbc error: exit status 128, detail: fatal: unable to access '<https://git.rancher.io/rke2-charts/>': Insufficient randomness
, handler helm-clusterrepo-download: update failure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-rke2-charts/675f1b63a0a83905972dcab2794479ed599a6f41b86cd6193d69472d0fa889c9 reset --hard HEAD error: exit status 128, detail: fatal: Unable to create '/var/lib/rancher-data/local-catalogs/v2/rancher-rke2-charts/675f1b63a0a83905972dcab2794479ed599a6f41b86cd6193d69472d0fa889c9/.git/index.lock': File exists.
Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.
, requeuing
the command I am using to start it up is this:
$ sudo docker run -d --name=rancher-master --restart=unless-stopped --privileged -p 8088:80 -p 8444:443 -v /volume1/docker/rancher:/var/lib/rancher rancher/rancher:latest --no-cacerts
elegant-truck-75829
07/23/2024, 8:45 AMsquare-fish-4786
07/23/2024, 8:47 AM2.9.0
so we can use it again to manage some EKS clusters with k8s 1.30
.
Is there any ETA? 🙏swift-farmer-84003
07/23/2024, 8:49 AMJul 23 08:46:43 cp-1 rke2[11624]: time="2024-07-23T08:46:43Z" level=info msg="Pod for kube-apiserver not synced (pod sandbox not found), retrying"
Jul 23 08:46:45 cp-1 rke2[11624]: time="2024-07-23T08:46:45Z" level=warning msg="Failed to list nodes with etcd role: runtime core not ready"
Jul 23 08:46:53 cp-1 rke2[11624]: time="2024-07-23T08:46:53Z" level=info msg="Waiting for API server to become available"
Jul 23 08:47:00 cp-1 rke2[11624]: time="2024-07-23T08:47:00Z" level=warning msg="Failed to list nodes with etcd role: runtime core not ready
I did put a token in config.yaml
token: my-shared-secret
tls-san:
- <http://my-kubernetes-domain.com|my-kubernetes-domain.com>
and just this from the docs
curl -sfL <https://get.rke2.io> | sh -
systemctl enable rke2-server.service
systemctl start rke2-server.service
brainy-country-46062
07/23/2024, 2:13 PM--flannel-backend=host-gw
. While it all works great, it causes hundreds of ports to be used on the host. Is there any way to control the port ranges used for all these inter process comms? As far as I can see it is nothing to do with nodeport ranges, I see lots of, for example, 43xxx, 44xxx, 45xxx, 48xxx, 57xxx and plenty of others.cold-crayon-13540
07/24/2024, 11:24 AMcold-crayon-13540
07/24/2024, 12:58 PMmelodic-planet-23258
07/24/2024, 1:05 PM0755
but this gets changed to 755
which is wrong and if I try setting it as string it gives me a type-error. How can I set the defaulMode correctly to 0755
?creamy-hydrogen-51032
07/25/2024, 4:06 AMsalmon-morning-84088
07/25/2024, 8:32 AM<http://users.management.cattle.io|users.management.cattle.io>
CRD been updated recently? I have previously set state: active
in the YAML of my users, but it feels like that field has been removed?curved-piano-98970
07/25/2024, 1:15 PMpanic: unrecognized command: pre-upgrade
and not being able to upgrade longhorn 1.4.3 to 1.5.5 anyone able to help?limited-pizza-33551
07/25/2024, 2:00 PMhundreds-printer-64563
07/25/2024, 3:22 PMhost.minikube.internal
using rancher desktop?ancient-doctor-54536
07/25/2024, 3:35 PMopenssl s_client -connect localhost:443 | openssl x509 -noout -dates
on one of the rancher MCM host, I still see the expired certs. The updated cert is showing correctly on the web browser and I can use kubectl perfectly fine on the rancher cluster so I feel like I'm missing a step. Could someone point to me what steps I may have missed? I've followed this documentation:
https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/update-rancher-certificatenice-businessperson-14225
07/25/2024, 8:21 PMmany-helmet-6962
07/25/2024, 9:48 PMadamant-kite-43734
07/26/2024, 3:01 AMhundreds-actor-42498
07/26/2024, 3:39 PMvagrant up --provider=virtualbox
.
Setup:
Vagrant 2.4.1
- Plugin vagrant-vbguest v0.21.0 (with v0.32.0 i get the error No VirtualBox Guest Additions installation found. More details can be found here)
- Plugin vagrant-vboxmanage v0.0.2
VirtualBox version 7
Detailed error log:
node-01: Destroying VM and associated drives...
C:/Program Files/Vagrant/embedded/gems/gems/i18n-1.14.1/lib/i18n.rb:210:in `translate': wrong number of arguments (given 2, expected 0..1) (ArgumentError)
from C:/Users/usr/.vagrant.d/gems/3.1.4/gems/vagrant-vbguest-0.21.0/lib/vagrant-vbguest/middleware.rb:24:in `call'
from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/action/customize.rb:43:in `call'
from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
..
damp-optician-31010
07/26/2024, 9:02 PMdamp-optician-31010
07/26/2024, 9:02 PMdamp-optician-31010
07/26/2024, 9:02 PM