Skip to content

Step 3: Setting Up a Docker Bridge Network in Container Manager

Important or Recent Updates
Historic UpdatesDate
New DSM7.2 Container Manager Update22/04/2023
Historic updates

We are now going to set up a Docker Bridge Network, we are doing this for consistency across the guides here. It also allows us to have more control over the ports containers use in case we want to avoid certain port ranges that DSM uses.

While most containers will happily work without doing this step it is good practice to set up a specific Bridge rather than using the default bridge or Network Host mode.

Let’s Begin

Open up the Container Manager and go into the Network tab.

Next click on ‘Add’ which brings up the settings screen. In here we are going to specify the following values.

SectionSetting
Network Namesynobridge (you can change this if you wish)
IPv4 ConfigurationManual
Subnet172.20.0.0/16
network: iprange172.20.0.0/16
Gateway172.20.0.1

Now click ‘Apply’ which will take you back to the original screen.

That’s it the Bridge is now ready for containers to be attached to it. You can go back to the guide you were following.

Optional Steps if you have the Synology Firewall Enabled

If you have the Synology Firewall enabled and configured to block incoming or outgoing connections you will need to do this step. Otherwise, you will have issues with your containers being able to contact each other.

Go into Control Panel > Security > Firewall

Click on Edit Rules and in the screen that appears click on ‘Create’

In the first screen select ‘All’ and ‘Specific IP’ then press ‘Select’

Then select ‘IP Range’ and enter ‘172.20.0.1’ in ‘From:’ and ‘172.20.255.254’ in ‘To:’

Press OK until you are back to the main Firewall screen and press Apply.

You can now go back to the guide you were following.

21 Comments

  1. Ryan Ryan

    Hi, what is the advantage of setting up a new bridge instead of using the default one? Thanks!

  2. John Klimaszewski John Klimaszewski

    One more question. There are two ports that you can apply to your container: local port and container port. What is the difference? I used to point to the Edgebridge by typing http://192.168.168.x:8088 for example. Is this the local port or the container port or can they both be the same?

    • Dr_Frankenstein Dr_Frankenstein

      So Local is the one exposed to your network and the Internal in the one the container is using (local left : Internal container right). For most of the time they are the same, the exception is if the local port is not available so you are free to generally change to what ever you want to, however the internal container port generally can only be changed using the actual app inside it first.

  3. John Klimaszewski John Klimaszewski

    If I am using an Edgebridge or proxy server don’t I need to change the up address to the up address of the nas so I can point to the Edgebridge proxy server? Currently you show a 172.x.x.x but my up address of my nas is 192.x.x.x so how would SmartThings know to find 172.x.x.x since this isn’t the assigned network addressing of my network.

    Thank you,

    John

    • Dr_Frankenstein Dr_Frankenstein

      Hi John

      The bridge network is purely for internal docker communication so your existing setup of using the NAS IP should continue to function as normal, the bridge is purely for the container(s).

  4. John Klimaszewski John Klimaszewski

    I am trying to setup an Edgebridge for my SmartThings app to get updates from weather services. I am confused on how to setup the network. In the old docker I just setup a port and point SmartThings to the up address of the Synology nas but this doesn’t seem to work anymore. Any advice for me?

    Thank you, john

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

drfrankenstein.co.uk – writing Synology Docker Guides since 2016 – Join My Discord!