Hi folks, hope your weekend is going well.
So I have put myself into a situation. I have a home server with docker installed running fine so far. In my home network I have multiple networks for different purposes. The whole network stack looks like this OPNSense — Switch — Ubuntu Server
The server is connected to a switch port with pvid 100, and runs on vlan0.100 Now my goal is to move some docker containers to other vlans. To accomplish that I have set vlan0.101 and vlan0.102 on my server as interfaces with their own IP and default gateway on that subnet (e.g. 192.168.101.10) Next step I set up macvlans for my docker containers Then I set the port to also allow tagged traffic, but kept it on pvid 100. Now on my OPNSense I changed the host ip of my server from 192.168.100.10 to include all 3 IPs so homeserver 192.168.100.10, 192.168.101.10, 192.168.102.10
This setup seems to work fine for internal network, however no services are reachable from the outside (internet) anymore.
My first question is: Am I thinking correctly about this? Or is this over-engineered bs at this point and there is a better way to put docker containers on different subnets.
Second question is: Any ideas what’s breaking the internet access?
Thanks for the help in advance :D
EDIT: i have not changed the vlan of any container yet
Bridge? There’s your problem I think. Bridge doesn’t allow ingress to individual IPs. In bridge, you tell each container what port it listens on, then access it from the IP of the host.
User defined bridges act differently from the default one as well. May not be relevant to your issue, but https://docs.docker.com/engine/network/drivers/bridge/#differences-between-user-defined-bridges-and-the-default-bridge
I mean at the moment I don’t have any bridges setup (other than the dockers own bridge) I thought maybe I could solve my issue with bridging
Oh, hmm. How are you telling which service to be on which IP then? Could you safely post your compose file?