https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
e
The failing command seems to be 
etcd-snapshot list --etcd-s3=false
Running it manually, it shows > WARN[0000] Unknown flag --protect-kernel-defaults found in config.yaml, skipping > WARN[0000] Unknown flag --system-default-registry found in config.yaml, skipping > WARN[0000] Unknown flag --token found in config.yaml, skipping > FATA[0000] open /opt/local/rancher/rke2/server/token: no such file or directory That file is indeed missing > [root@k8s-master-03 server]# pwd > /opt/local/rancher/rke2/server > [root@k8s-master-03 server]# ls -la > total 12 > drwxr-xr-x 3 root root 4096 Jan 25 18:13 . > drwxr-xr-x 4 root root 4096 Jan 25 18:13 .. > drwxr-xr-x 3 root root 4096 Jan 25 18:13 manifests
Do note, I changed Advanced -> Data Directory configuration value from 
/var/lib/rancher
to 
/opt/local/rancher
c
Check the rke2-server logs. The checks are all erroring because rke2 hasn't started yet.
đź‘€ 1
e
where would I find them ?
Aha, 
jourlnalctl rke2-server
It shows
time="2025-01-25T181304Z" level=fatal msg="failed to parse system-default-registry: registries must be valid RFC 3986 URI authorities: jfrog.proxy.internal.io/docker-hub-remote"
Damn, but if I change the default registry, then Rancher setup will fail due to an incorrect registry, as I can't set rewrite rules there...
c
You need to use rewrites in the registry mirror config, instead of setting system default registry. Containerd does not support modifying the image name just by appending a path to the registry address.
Check the rke2 docs on how to set up your jfrog repo as a mirror for docker.io and enable rewriting the image name.
And then leave the system default registry field blank
e
Not the owner of the frog repo. But thanks for the info regarding rke2-server ! I'll try once more !
Hmm, If I change 
system-default-registry
from 
<http://jfrog.proxy.internal.io/docker-hub-remote|jfrog.proxy.internal.io/docker-hub-remote>
to 
<http://jfrog.proxy.internal.io|jfrog.proxy.internal.io>
then my local cluster 
fleet
starts to error
Failed to pull image "jfrog.proxy.internsl.io/rancher/shell:v0.3.0": rpc error: code = NotFound desc = failed to pull and unpack image "jfrog.proxy.internal.io/rancher/shell:v0.3.0": failed to resolve reference "jfrog.proxy.internal.io/rancher/shell:v0.3.0": jfrog.proxy.internal.io/rancher/shell:v0.3.0: not found
because it NEEDS a namespaced registry
This works
<jfrog>*/docker-hub-remote*/rancher/shell:v0.3.0
This does not
<jfrog>/rancher/shell:v0.3.0
Manually added 
registries.yaml
to the k3s local cluster. That seemed to solve my issues
i don't know how all of this worked magically 4 months ago when I tested this switch to new OS+Rancher+Cluster
c
yes. if you need to change the namespace then you need to rewrite. You can’t just append it to the registry hostname.
e
I seem to got it working! Thank you so much for pointing me to the right docs and directions !
170 Views
Open in Slack
PreviousNext
Powered by