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.

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

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 ‘’ in ‘From:’ and ‘’ 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.


  1. Seth Watt Seth Watt

    I have a mediabridge network defined,
    IP range:
    IPV6: Disabled
    IP Masquerade: network:enable
    Container: bazarr, sabnzbd, prowlarr, snarr, radarr, jellyfin

    Every time the sabnzbd container restarts, the IP address it’s using changes, so sonarr and radarr can’t find it. I have to manually update the download client in those apps.

    Do you know how I can force it to keep the same IP?

    Thank you again!

    • Dr_Frankenstein Dr_Frankenstein


      So you can just avoid using the IPs for the individual containers and make use of the DNS docker will do πŸ™‚ – So use for all your containers to communicate, and they will just work regardless of IP changes.

  2. Peter Peter

    Good day, what else do I need to set because I can’t get to the address of the bridge.
    As DHCP, I use a router that assigns addresses from the network. The NAS has an address of The docker bridge is for portainer, but I can’t get to I also set up a firewall on the NAS according to your instructions. Thanks for answer

    • Dr_Frankenstein Dr_Frankenstein

      Hey, keep in mind the bridge is not exposed externally, it is purely used between containers. Your containers will expose any WebUI / Ports on the NAS IP and Port.

  3. Adam Adam

    Hello! I am a total noob trying to get this set up. I am using docker (I think a different version than you show here) and there is no tab for “project”, though the rest looks pretty much the same. Do I need a different version, or is there another way to create a project?

    Thanks for these guides! Very helpful!

    • Dr_Frankenstein Dr_Frankenstein

      Hey, it sounds like you have the ‘Docker’ package rather than ‘Container Manager’ either you need to update DSM to the latest version to get access to the new package or see my ‘Archive’ on the left menu with guides for the older docker package which should all stick work well.

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. – writing Synology Docker Guides since 2016 – Join My Discord!