May this helps: this is the ifconfig output for OMV:ĭocker0 Link encap:Ethernet HWaddr 02:42:10:92:42:aa and also opening 172.17.0.2:8080 doesn't open the rutorrent webinterface. I still cannot ping 172.17.0.2, which is the ip adress the docker image is assigned to.

Beware that this extra options don't come back when you use the modify container option.Īs usual docker docs get much better with time and this function is well explained hereĪdding those entries allows me to connect to the OMV Webui by typing 172.17.0.1 in the adress bar in my browser. In the plugin you will probably need to specify no network and run the ip assignment in the extra option. The plugin has no support for macvlan, so you need to first drop down to CLI to create the macvlan network. I am not sure but you can probably assign MAC address to each run/create container so you can control the assignment with the DHCP server. You can assign ip address at the run/create of the container. If you want to use your local network scope you need to use macvlan driver, creating a macvlan network. Network data from the containers get a MASQUERADE entry also in the nat table. The bridge mode has nothing to with the local network, the docker0 is a network bridge for all containers, the default subnet is 172.17.0.x.Įvery port forward we put is a DNAT entry in the nat table. It looks like that's the cause of the problem. However in my router this MAC adress doesn't show up (and so there's no IP being assigned). Thanks again, the container is said to be running in OMV webUI, also I cannot find anything strange in the container details settings (see snippet underneath)

Docker for mac bridge ip