Open chrisnruud opened 1 year ago
jandubois
commented
1 year ago I don't think there is much that Rancher Desktop can do about, beyond not setting up the bridged network, as that is all managed by Apple's VMNET. If you disable "Admin Access", then it won't be able to request the bridged network (the daemon talking to VMNET must run as root), and will just use port forwarding to localhost.
jandubois
commented
1 year ago Oh, the other thing you will lose by disabling admin access (if you are using moby) is the docker socket in the default location /var/run/docker.sock. But a docker context called rancher-desktop will be created, and normally selected automatically. Run docker context use rancher-desktop if that doesn't work. Or if you use software that doesn't know about docker context, set up DOCKER_HOST.
Actual Behavior
My mac is using passwordless 802.1x discovery at work based on network interface MAC address - and this works fine normaly, but when I launch rancher desktop and it sets up bridged networking, the ethernet interface loses connectivity and only registeres as "not conencted", meaning that there is some kind of interference with the discovery or the hardware address on the broadcasted ethernet interface.
Steps to Reproduce
Result
access to the hardwired network disappears
Expected Behavior
rancher should run as well as the hardware network still announcing itself properly so that the switches configured using 802.1x patches the ports to the correct network
Additional Information
No response
Rancher Desktop Version
1.11.0
Rancher Desktop K8s Version
not appliccable
Which container engine are you using?
moby (docker cli)
What operating system are you using?
macOS
Operating System / Build Version
macOs Sonoma 14.1
What CPU architecture are you using?
arm64 (Apple Silicon)
Linux only: what package format did you use to install Rancher Desktop?
None
Windows User Only
No response