I'm a noob here on unraid, but switched out from Synology and loving it..

I've running the latest version as well, and have got 3 NIC's connected.   with about 20 dockers.  

Using 1 dedicated NIC to allow me access to the portal, as I find that sometime the GUI drops and I have to restart, but that's not the main issue.

Other two NIC have been excluded from the portal.

I've got 1 NIC dedicated to the Docker network with the Gateway set, on a vlanID.  Controlled through my Unifi Switch.

1 NIC dedicated for SMB traffic on a different Vlan.

 

But overtime I configure a docker app, it use the portal address, with Host,Bridge set. all with the same IP Address as the portal.

Switch it over to the Custom Network, which is the vLan, but then it dishes out IP address for each of the dockers.  ie: 10.5.50.2/3/4/ etc.

I wanted to all use the main NIC address, unless told it.

 

I've got Macvlan enabled, as IPvlan is grey'd out.

I guessing there is a simple answer and I'm just missing it.

 

Portal - 10.5.1.10

Docker - 10.5.50.10

SMB - 10.5.20.10

 

I did try it with LAG setup but still the same.

 

Any help would be appreciated.

Not really my thing, but did you unselect the other networks from docker settings? Leave only the dedicated network selected, then host and bridge should use that network, because if you select custom, you are supposed to assign a specific IP for that container.

Yes,   the only one selected in the docker settings is the NIC i want.

Than that should be the NIC used in host and bridge mode, are you seeing something different?

yes, they are all using the eth0 NIC as mentioned, all the dockers if set to host or bridge are using the main IP address (with the ports)

So All dockers are given the 0.5.1.10:xxxx addresse - Even though this is no selected in the Docker Settings.

 

When I select the eth1 address, dockers are then provided with unique addresses from the NIC's address - which is supplied by the Unifi Switch.

1st Docker gets -  10.5.50.2

2nd Docker gets - Docker - 10.5.50.3

3rd Gets Docker - 10.5.50.4

and so on and so on... 

 

I had it wrong, the custom networks options if only for when you select a custom network, and for that you then have to use a custom IP, if you use bridge/host it will always be based on eth0, so what you are seeing is how it works.

Thanks for the quick response.   Glad to know that I'm not seeing something.

If that's the case, then I'll move the eth0 to the docker network and then make eth1 the portal.

Turns out you can't exclude eth0 either, so I can't configure the way I want too 😞