https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
p
Does running 
wsl --install --no-distribution
as mentioned in the error message provide any details?
l
It does not. Only output it that is completed successfully. But, it doesn't resolve the issue.
p
If you didn't already, you have to reboot after installing wsl with the VM optional component. You say you verified VM platform is enabled, but the error message says you don't have Hyper-V installed. If the simple install command doesn't work for some reason, you may need to go through the manual steps: https://learn.microsoft.com/en-us/windows/wsl/install-manual
l
Apologies. I'm not very familiar with any of this. When it says to verify all of this stuff, does it mean on my host machine, or in the VM OS?
None of the information I'm reading clarifies at all if they are talking about on my host machine, or on the VM instance.
This is on my host machine.
p
On the host. If this error is correct, there shouldn't even be a VM because Hyper-V isn't actually installed yet. After checking the box here for it, you need to reboot Windows to actually install it. But if you already did that, something else is wrong.
You may still have wsl working, but it's wsl 1 which doesn't use a VM
l
There absolutely is a VM running.
In this VM instance is where I have installed Rancher-Desktop.
p
Yeah that's Hyper-V, so is that error screenshot you posted actually current or are you getting a different error after fixing that one?
l
The error screenshot is the only error I'm getting for now.
p
Not sure why then. The error says Hyper-V isn't installed, but it obviously is if you have a VM running in it.
l
I am not able to figure out why WSL2 is not supported in my current VM instance.
p
Are you trying to run Rancher Desktop in a Windows VM?
l
Yes.
p
Ah well in that case you need Hyper-V installed and working in the VM. I'm not sure that will work because a lot of computers don't support nested virtualization.
l
Hmm. Ok. I'll try then next then. Thank you.
b
@limited-hospital-45328 I think you will also need a 
.wslconfig
file in the users directory with the nested virtualzation set to true...
l
@bored-farmer-36655 On my host machine, or in the VM Windows instance?
b
@limited-hospital-45328 The vm, but I see it's WSL2 and Windows 11 , but some other options may help <https://learn.microsoft.com/en-us/windows/wsl/wsl-config#main-wsl-settings>
l
Ok. Thank you.
p
To be clear; you needed to run 
wsl --install --no-distribution
in the Windows VM, same with all the instructions about installing Hyper-V bits / Virtualization Platform stuff. (WSL is based on bits of Hyper-V; so you'll be using a nested VM here)
The instructions never talk about it because you'd be treating your (Windows) VM as a bare metal machine, kind of.
l
Ok. In that case, I ran the command in both my host and the VM instance, but it didn't work.
b
@limited-hospital-45328 So is this Windows VM 10 or 11?
l
11
b
@limited-hospital-45328 and how many cores/ram allocated?
l
4 cores. 8192 mb ram.
b
@limited-hospital-45328 any more joy? So I did setup a Windows 11 Pro VM on openSUSE Tumbleweed and libvirt, installed Rancher-Desktop and had fun with kubernetes certs (@proud-jewelry-46860 the k3s-versions.json was missing?) I also configured wslconfig to use 4 cores and 8GB of ram and all good... the VM has 8 cores and 32GB of RAM
l
Ok. The last thing I tried last night was enabling Hyper-V on the Windows VM Instance, but still no luck. Oddly, the first time I enabled it, it went through all the rigga-ma-roll of appearing to install the requirements for Hyper-V, but after a restart, it was still NOT enabled. So, I ran it again, and after another restart, it was then enabled.
But, that did not fix the issue. The error still says Hyper-V is not installed.
I haven't been able to focus on it much today as I have a client meeting today I had to prep for.
b
If you open the Task Manager and select the Performance Tab, does it show Virtualization as enabled?
l
Oddly, in my Windows VM, I don't even see a Virtualization option. On my host machine, I do see 
Virtualization: enabled
Not sure why I don't have that field at all in my VM.
On my Windows VM, where I see Virtualization on my host machine, I have "Virtual Processors, and Virtual Machine"..
b
Oh, your on a Laptop.... Hyper-V conjured up a sever...
So is the host system locked down, hence the vm?
l
I'm not sure how to check that it is locked down.
b
I mean can't you just run Rancher-Desktop on the host?
l
Oh. I can. lol It's a long story. I am having a docker compose issue with my application that I work on for my client. And everyone keeps suggesting that I start with a fresh desktop and see if I still have the same issue when trying to compose the app from there. So, I've created this VM and am just trying to set it up so I can try to compose the app and see if that issue still persists there.
So, this Rancher Desktop issue isn't even the main issue I'm trying to resolve.. lol
I'm just adding to the pile I guess. lol
b
Ahh ok, so just creating another user and installing rancher desktop would not be an option? Perhaps use Virtualbox instead?
l
I originally tried Virtualbox actually, but for some reason there, it wouldn't even complete the Rancher Desktop install. It just kept freezing. I let it go for 6 hours earlier this week, and it never moved an inch..
b
So using another user, or just wsl on the host with a linux distribution and install docker etc there?
l
Hmmm. I could try that. Just creating another user on my host machine will not have any "potentially cached" issues that my admin user might have?
b
It shouldn't and just install Rancher-desktop for that user only
l
Ok. Should I uninstall it from my admin user? It is currently installed on my admin, and doesn't seem to have any issue there.
I believe the issue I'm having with my application is a dependency issue.
loopback-connector-firestore to be specific.
b
So Rancher-Desktop worked as another user 😄 and resolved your issue....
l
Lol. I haven't been able to try it yet. Had meetings all afternoon. I will try it first thing tomorrow and update you.
Open in Slack
PreviousNext
Powered by