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.

6 Comments

  1. Jim Jim

    Hey, Dr. F! Great guides, one issue for me though…. when I amend the temp/completed/watched folders for Sabnzbd in settings, it gives me a failed error and says it cannot create directory /data/usenet/xxx

    Any thoughts?

    • Dr_Frankenstein Dr_Frankenstein

      Hey, if it’s just for SAB check you used the correct PUID/PGID values and the right way around.

      • Jim Jim

        That was the first thing I checked… All correct. It’s a problem with all: sonarr, radarr and sabnzbd (these are all the containers I did besides plex). Thx!

        • Dr_Frankenstein Dr_Frankenstein

          OK if its all of them check that the dockerlimited user is showing in the dockergroup and they have the appropriate permissions assigned to the /data share. If that is correct can you reach out via my Help Me! page please.

  2. James James

    Hi there – thanks so much for these guides! This may be a silly question… but for the IPv4 steps, should I be replacing your 122.xxx addresses with my own IP address? Thank you 🙂

    • Dr_Frankenstein Dr_Frankenstein

      Hey, not a silly question. Use the same one in the guide. It keeps things consistent and when going through some guides I suggest specific IPs to use which marry up with this guide 🙂

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!