https://rancher.com/ logo
#kubernetes
Title
# kubernetes
a

adamant-kite-43734

11/28/2022, 1:26 PM
This message was deleted.
v

victorious-guitar-37937

11/28/2022, 2:34 PM
the kube-api logs are full with
Copy code
I1128 14:32:48.479587       1 client.go:360] parsed scheme: "passthrough"
I1128 14:32:48.479808       1 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{<https://116.203.221.182:2379>  <nil> 0 <nil>}] <nil> <nil>}
I1128 14:32:48.479843       1 clientconn.go:948] ClientConn switching balancer to "pick_first"
thats the only uncommon thing i could find within the kubernetes cluster
I might have looked completly in the wrong direction, seems to be a cgroup problem
b

billions-honey-62634

11/29/2022, 4:22 PM
You have to troubleshoot with
docker logs <container id>
Running rancher in single node docker is only recommended for testing. From the docs
A Docker installation of Rancher is recommended only for development and testing purposes. The ability to migrate Rancher to a high-availability cluster depends on the Rancher version:
Install Rancher on top of a HA Kubernetes
kube-api listens on 6443, the docker container spins up a single node k3s "cluster", looks like there is something preventing the container or k3s to start up properly
v

victorious-guitar-37937

12/01/2022, 10:42 AM
thanks for the help,
docker logs <rancher-id>
only shows that there is no connection. If i inspect the container and got to the mounted
/var/lib/rancher
folder i can see further logs like
k3s.log
that yield further information why k3s does not start. That took me hours to figure out 😞 But atleast I have a new angle for my troubleshooting.
52 Views