This message was deleted.

You're removing admin rights from inside the VM? That's… going to be lots of fun technical challenges, I think. Especially since k3s normally is run as root in the VM, so whatever answer I provide here would be incompatible with what you're doing… Currently the provisioning scripts run earlier than that; you could manually enter the VM and run Kubernetes manually there if you wanted to, but it'd be outside the control of Rancher Desktop (so if things break you get all the pieces).

@proud-jewelry-46860 we’re disabling admin on the local machine, not the VM. The main issue seems to be the Kubernetes installation.