This message was deleted.
# rancher-desktop
a
This message was deleted.
w
so i think this is more of an it depends. https://lima-vm.io/docs/config/network/
i know i still am seeing qemu egress vs the apple hypervisor nat
f
Thanks Justin, I tried interacting with the configuration with no success; I had not found the doc you shared though. I'll go through the doc and try again.
w
yeah rd just uses limavm for interacting and maintaining the vm
f
Typically the bridge network is defined in docker networks though; not sure if Lima is setting those up...
Copy code
bm@bmac~/Library/Application Support/rancher-desktop/lima/_config$ docker network inspect bridge
[
    {
        "Name": "bridge",
        "Id": "134ab611c0ee4ae9f2c027358323f9dd53901a2c79f3b7414ef61b523079dec3",
        "Created": "2024-05-07T15:03:35.441326008Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.17.0.0/16",
                    "Gateway": "172.17.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {
            "com.docker.network.bridge.default_bridge": "true",
            "com.docker.network.bridge.enable_icc": "true",
            "com.docker.network.bridge.enable_ip_masquerade": "true",
            "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0",
            "com.docker.network.bridge.name": "docker0",
            "com.docker.network.driver.mtu": "1500"
        },
        "Labels": {}
    }
]
The Lima docs say
# bridged mode doesn't have a gateway; dhcp is managed by outside network
.
That makes me think it doesn't set up the bridge in docker networks.
w
well if you use bridged instead of NAT, but i would assume you are using nat
f
This has nothing to even do with container networking. The bridge network is used internally as well so for instance; if I have no containers and I only want to pull an image from a registry, it fails to pull if the registry server is on the 172.17 network (which is my case). I need to change the default bridge network so I can pull images.
Ok, found the problem! If you want to change the bridge network you must
rdctl shell
and edit the /etc/docker/daemon.json within the VM itself. Rancher Desktop ignores your desktops /etc/docker/daemon.json