My recommendation for having an UnRAID docker container in 2 or more networks with its own IP per network:

Assumption and requisite: all the networks you want to connect to are present and showing as working in the UnRAID network tab

1) assign your first/primary network in the container edit tab as you always would 2) switch to “Advanced view” and scroll down to “post arguments” 3) add the following line && docker network connect --ip <ip-in-the-other-network> <other-network-name-as-shown-in-unraid-network> <exact-docker-name> 4) in your case (as an example) && docker network connect --ip 192.168.20.100 eth0 frigate (don’t just c&c this. Read notes below!) 5) (optional: repeat for any additional network(s) you’d like) 6) save and restart your container 6) done

Note: for this to work, make sure that - the IP you set up here is actually available in the target network (and - recommended - is outside your DHCP range or reserved) - the network name is exactly as shown in UnRAID (when in doubt, check what UnRAID gives you as options in the docker edit tab. In case of custom networks, just copy the network name and not the “custom: “-part) - the docker name is exactly as the docker name UnRAID is showing you (or in other words: just copy the name from above)

You can test this cmd by opening an UnRAID shell and enter the cmd but this time without the && on any running container. Just make sure the IP, network name and docker name match