VPN tunneled access for docker is forced on all containers, even the ones set to use Host and Bridge networks

[BestITGuys]

I have it set up in VPN Manager (tunnel called wg0), and it's generally working as expected. I have specific containers set up to use the custom wg0 network, and those are the only containers that I want tunneled through it. However, that tunnel is being enforced on all other containers as well (anything using the Bridge or Host networks), and I don't see any reason why that's happening. The way I realize that this was going on is because I checked my public IP address from those containers, and they're reporting the tunnel's IP instead of my actual public IP.

 

Is this expected behavior, and if so, how can I change it so that the Bridge and Host networks don't get forced into the tunnel?

 

Update: when I disconnect the wg0 tunnel, the containers that were specifically assigned to use that tunnel completely lose their connection (as expected), but the rest of the containers revert to having the correct public IP. And as soon as the wg0 tunnel is reconnected, they start showing the public IP of the tunnel again

Edited September 12, 2024 by BestITGuys