If you have an Ombi container, and a Sonarr container (or Radarr/Lidarr/CouchPotato etc), then these services will all need to talk to each other. Docker would see the traffic hit the host on 3589 and pass it through (via Network Address Translation, or 'NAT') to the container on 172.17.0.3:5000 Talking to Other Services ¶ To access the service from outside of the Docker host, you'd browse to the LAN IP of said host and the port you mapped - 3589 in the example above. The two ports do not have to be the same - you could map 3589 on your host to point to 3579 on your container. This means that you map ports from the host to the container, much like port forwarding for access from outside your network (as you would for passing ports 80 and 443 to your web server, for instance). If the Ombi container was given 172.17.0.3, then it would listen on 172.17.0.3:5000 (for example). Usually, Docker uses 172.17.0.x for these. Bridge ¶īridge networking makes the Docker Host behave like a VM Host and a router, with a whole separate virtual network behind its own LAN IP.Įach container then gets an IP in a whole different IP range than your LAN itself. It is appropriate for some systems (like Home Assistant), but one of the benefits of Docker is the 'isolation' of services (so nothing depends on anything else). This means that the container runs like any other network application, with complete freedom to discover other devices/services on your network. Host networking gives the container direct access to the network adapter of the host machine (the one running Docker). Open Ombi " and setup your ombi installation.Ĭonsiderations ¶ Host vs Bridge Networking ¶ Host ¶
0 kommentar(er)
