I'm trying to give a docker container port 80, but that port is used by unraid's gui. I found out that 6.4 supports passing VLAN ips to docker, so I updated. However, after creating the VLANs, all the IPs that I added simply route to unraid itself again. 

 

Looking at the bottom of my networking settings, I see a Routing Table, and in it I see three entries for 192.168.1.0/24 -- my main br0 and the two VLANs I made, br0.201 and br0.202. My guess is that because my vlan IPs fall within 192.168.1.0/24, when I try to connect to the VLANed IPs, it just hits br0 and unraid takes it. Under Docker settings, I see a few options for 'DHCPv4 pools, but they all correspond to 192.168.86.1.0/24, not the explicit IPs for the VLAN. 

 

Any ideas?

VLANs are supposed to be independent networks (they can talk to each other via a gateway or router)

Assigning the two VLANs with the same IP subnet is not going to make them magically talk to each other, unless you have a router and the router is configured and properly distinguishes between the thre VLANs

 

In my case,

I have a router with the following networks

VLAN 0 (Main network) - 192.168.2.0/24

VLAN 3 (Containers) - 10.0.3.0/24

and router is setup to make them both meet.

I didn't bother assigning an IP to the unRAID VLAN 3 interface, as that would make the network stack attempt to communicate directly to the continers, which fails due to docker macvlan networking (which is the system used to provide the containers their own VLAN network on the same interface and the unRAID)