This message was deleted.
# rancher-desktop
a
This message was deleted.
f
You can if you are on macOS and are running with admin privileges. In that case Rancher Desktop will create a bridged interface that is reachable on the local network. This may not work if you are on Wifi and not on a wired network because Apple doesn't support bridged interfaces on the Wifi adapter (although sometimes it seems to work anyways).
Look for the IP address of the
rd0
interface with
rdctl shell ip a
f
thanks, I’ll play with this later. I was playing around with colima and was not having any success. Would the IP address be on my LAN - like it would get it from DHCP? I am using wifi right now so maybe that had something to do with it
oh, extra details - my usecase is I’m on a m1 mac and I need to run x86 containers on k8s, so I’m trying to do all the rosetta emulation stuff
f
Yes, the bridged interface
rd0
should have an IP address from DHCP on your local LAN. This is nothing to do with using VZ or Rosetta, but only depends on having admin access (the bridged network daemon needs to run as
root
), and the host interface support for bridging. Check for the
rd0
interface inside the VM. If you don't have it, then you don't have a routable address
f
s
sorry, in multiple terminals
f
Actually, also check that
rd0
has an IPv4 address. If the interface exists, but has no address, then the host adapter doesn't allow the bridging.
We have not been able to figure out when exactly bridging works over Wifi. Some people have it working on their home Wifi, but not the corporate one...
f
I don’t seem to have that interface
f
Do you have Admin access enabled? General | Rancher Desktop Docs
f
yep, that’s checked. do I need to turn on this
socket_vmnet
thing?
f
No, that won't make a difference. Let me check on an M1 machine...
Oh, wait, you do need
socket_vmnet
if you are using
VZ
. Unfortunately there is a bug in Rancher Desktop that incorrectly assumes that it doesn't work with VZ and ignores the setting, even when enabled. This will be fixed in 1.10, but for now you are out of luck 😞
f
can I go and tweak a config file or something? 🙂
f
No, it is hard-coded in the source 😞
f
oh well. Guess I’ll just spin up an eks cluster or try to bang my head against colima some more ¯\_(ツ)_/¯
thanks for clarifying though
So it isn't even fixed yet, but looks like I created the issue and assigned it to myself, so should have realized this earlier 🙂