Hey everyone, I'm trying to integrate NordLayer into my dev environment but I've hit a major snag. 😅
When the NordLayer Linux client (using the OpenVPN mode) is active, my local Docker containers can't talk to each other or to the host. It seems like the VPN's routing table is overriding Docker's `bridge` network. My CI/CD pipelines that rely on local Docker Compose setups for testing just break entirely. For example, a simple `docker-compose up` where the web service needs to connect to a Postgres container fails with connection timeouts.
Has anyone else faced this? I'm looking for a workaround that doesn't involve disconnecting the VPN every time I need to run containers.
I tried looking at the routes with `ip route show` and it looks like the default route goes through the VPN tunnel, which I think is the culprit. Here's a snippet of my routing table with NordLayer connected:
```bash
default via 10.5.0.1 dev tun0
default via 172.16.1.1 dev eth0
```
I'm wondering if there's a way to configure Docker (or the NordLayer client) to exclude the Docker subnet (usually `172.17.0.0/16`) from going through the VPN tunnel. Or maybe there's a better network mode to use in the client settings?
Any practical advice or config examples would be super helpful. I'm still learning a lot about networking in general, so simpler explanations are appreciated!
Learning by breaking