Bridge mode not working

[justsimon]

Hi,
I can't get Bridge mode to work when launching containers. I'm new to Docker, so I may be making a mistake.
I tried setting the ServerIP variable, but I can't ping that address.
Using Host mode works fine, I can access the application at the right port.

When I leave all the settings as default, the container gets whatever address but nothing new shows on my network. Sometimes the Details shows the ServerIP is something silly like 0.0.0.0 (see screenshot)

Am I doing something wrong, or is the Docker app not working quite right?

I'm using an F5-420
Running TOS 4.1.30-2008051459

[TMSupport]

Will test here first and get back to you later.

[justsimon]

Hi,
Have you had time to test this yet?

Have any other customers successfully got a container running in Bridge mode?

Cheers

[TMSupport]

Sorry, we get back to office from National Holiday today. Will get the result to you later.

[justsimon]

Hi,

So this is normal behaviour, I just didn't know how Docker bridge worked.
By default Docker manages the subnet 172.17. 0.0/16. You can add another subnet to assign IPs that will appear on your home network.

This raises a new question though.
I created a new subnet, let's call it NEWNETWORK, and there's also a default network option in Docker called None.
Neither of these are available in the Terra-Master Docker app, do you know why?

For other users, check out portainer.io for managing Docker on your TNAS. It offers far more functionality.

[JayBlingham]

I believe the TM folks said that Portainer is coming soon in this post (if I copied the link right):

viewtopic.php?f=12&t=910&p=4414&hilit=Portainer#p4414

[justsimon]

Cheers!

I got portainer set up over the weekend following a video made for Synology:
https://youtu.be/ToL5SPFUPaQ?t=330

It's really good!

[JayBlingham]

Nice! I’ll check it out. I’m soooo new to Docker, ans don’t know a whole lot, but I’m also sad I didn’t look into it sooner!