https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
w
you basically installed a parallel lima install. probably should look at https://docs.rancherdesktop.io/references/rdctl-command-reference/
f
thanks for the reply. i didnt start any new vm using limactl, i was hoping i could access details of vm started by rancher desktop using limactl. seems some config is missing for limactl to get this info. Also as you said, i figured i could access vm using 
rdctl shell
and do ifconfig to get the details. I tried adding route on my laptop from docker bridge network cidr to lima vm ip (which i got from eth0 from inside vm). --- This didnt work.
on vm itself i can see udp port being listened to. Didnt yet figure out how to open this onto my mac intel laptop.
i will also try changing the lima vm network to experimental sock-vmnet config and see if this might help.
w
you can use limactl, but you need to point it at the rd limahome and not the generic one. guessing you are dealing with https://github.com/lima-vm/lima/issues/366
f
Please don't use 
limactl shell
with the Rancher Desktop VM; it is very easy to get something wrong. Use 
rdctl shell
instead.
The 
eth0
interface is not accessible from the host; if you are using VZ emulation you should be able to use the 
vznat
interface. If you are using QEMU you must enable admin access to get a bridged network at the 
rd0
interface. This sometimes fails (depending on your local network config), so you can also try 
rd1
, which is a shared network accessible from the host, but not the LAN.
3 Views
Open in Slack
PreviousNext
Powered by