I’m at my wits end. I have tried multiple times to install Rancher and only one of them was successful (on Ubuntu, but I can’t use Ubuntu).
The most unsuccessful try is using this instructions here (option A):
Is this not the correct one? I can never connect to the docker with this method. Just get a “connection was reset” every time. One would assume the docker would be the easy one that just works.
I found a method called “rancherd” which worked perfectly on ubuntu when I tried it.
Any pointers would be greatly appreciated. So far, this has been one of the most frustrating installs I have ever come across.
The docker is just spitting out this in the logs. I tried this docker on multiple computers all with the same result. The docker is busted it seems. Any idea how long it’s been broken? Is Rancher not that stable?
2022/06/09 22:18:29 [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/06/09 22:18:31 [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/06/09 22:18:33 [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/06/09 22:18:39 [FATAL] k3s exited with: exit status 1
Hey @xamindar, sorry that you are having issues here. One warning here - the single node docker install is really a “quick-start”/ “test” item - it’s not a stable option for long-term or production usage. If you are looking to install rancher for production/long-term usage, you are going to want to use the k8s cluster option.
If you are just looking to get something basic running, you can continue to try and use the docker option. Keep in mind that it is trying to run an embedded k3s cluster inside of the image. Personally, I have seen this method struggle in resource-constrained environments. I’m not entirely sure how strong the nodes that you are using are, but I would recommend making sure that they are at least at the value outlined in our documented requirements. If you can describe your environment and os limitations a bit more, I might also be able to point you at a solution with a higher probability of success.
Thank you @MbolotSuse. My cluster is k3s on 3 raspberry pi 4s at the moment. I have a 2 core 4 g ram computer I am trying to use to test rancher. From what I gather, you are not supposed to run it (or can’t) on the same cluster you want to manage? In this case the pi cluster.
I’m not going to keep trying the docker as it seems to be pretty broken.
I’ll try installing on another cluster again and see if that works.