How do I change network subnets?

[robertmircea]

OrbStack subnets used for bridges conflict with my employer's subnets when connected to VPN. How can I change subnets used by OrbStack to create bridges for Docker and VMs?

❯ netstat -rn | grep 172.
172.18             link#48            UC          bridge102      !
172.18.255.255     ff.ff.ff.ff.ff.ff  UHLWbI      bridge102      !
172.19             link#52            UC          bridge104      !
172.19.255.255     ff.ff.ff.ff.ff.ff  UHLWbI      bridge104      !
172.20             link#50            UC          bridge103      !
172.20.255.255     ff.ff.ff.ff.ff.ff  UHLWbI      bridge103      !

[kdrag0n]

You can change Docker subnets with the standard Docker default-address-pools setting. For example, paste the following into orb config docker or the Docker settings tab:

{
    "default-address-pools": [
        {"base": "100.100.0.0/16", "size": 24}
    ]
}

This config will create networks like 100.100.0.x, 100.100.1.x, and so on.

Then recreate Docker Compose networks with docker compose down && docker compose up for it to take effect. You can also disable the bridges in OrbStack's Network settings.

The subnet for Linux machines isn't currently customizable, but you can subscribe to #218 for updates. It's not in the 172.x block.

We've just released v0.13.0 which improves compatibility between bridges (if enabled) and VPNs. Would you mind giving a try first? It should no longer be necessary to disable the feature when there are IP conflicts.

[robertmircea]

Docker works ok with proposed changes, but the subnets for the Linux machines still cause trouble. There are still overlapped subnets between VPN routed ranges and orbstack's bridges.

[kdrag0n]

As I said above, those are not Linux machines subnets, which are in a completely different range (currently 198.19.249.x).

What you're seeing is Docker Compose networks that haven't been updated because you haven't recreated your Compose networks after changing the settings. Either use docker network rm to delete them or recreate them by running docker compose down && docker compose up in each project. This is unfortunately just how Docker works. It's not an OrbStack thing.

Have you updated to v0.13.0? If not, please do because it should automatically avoid conflicts now. If so, please share log files from the Help menu.