This message was deleted.
# vsphere
a
This message was deleted.
👍 1
i
Hi, im having the same issue, were you able to figure this out?
l
Never did, basically just recreated the Rancher instance to fix it 🤷
i
Frustrating. I also tried re-creating rancher without any progress. Are you running Rancher on k8s?
l
No - running Rancher standalone using the docker container
i
maybe ill give that a shot. Would you be willing to share what steps you use to create your vsphere template? trying to rule things out as my problem
l
This is what I do
The networking stuff is because I don’t use DHCP, so after Rancher clones the template I set the IPs statically, then Rancher finishes the setup process
i
much appreciated, only step with deploying ova was setting password? did you install the packages listed here? https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/launch-kubernetes-with[…]des-in-an-infra-provider/vsphere/create-a-vm-template
l
When deploying the OVA there’s a spot to set the initial password so did that and then after deployed turn on and login and make a few changes for static networking and ssh auth. I didn’t install any packages, after Rancher creates the clones and the static IP is set (by me) it has access to the internet so Rancher might install some packages when it does it’s part, not sure…
🙏 1
i
Much appreciated in helping out a stranger. ill give rancher docker a shot and the ova template. We've been using packer for our RKE1 clusters.
👍 1
Was able to deploy an RKE2 cluster successfully using the docker image so thank you for your guidance. I've narrowed it down to
differences
of how Rancher runs in k8s vs a rancher app. Unclear what those differences are. RKE1 deploys just fine.