TerraMaster Forum

Posted: **18 Oct 2022, 23:00**

1) Create custom network:

docker network create custom_bridge

or through Docker Manager
2) Check ip address on the new bridge

ip a | grep br-

it should be like

inet 172.18.0.1/16 brd 172.18.255.255 scope global br-2becce7b1bb4

3) Check route

route -n | grep br-

it should be like

172.18.0.0     0.0.0.0         255.255.0.0     U     0      0        0 br-2becce7b1bb4

4) Run a new container in the new network

docker run --rm --entrypoint sh --network web nginx:alpine

5) Repeate №2 and №3
AR != ER
AR:

inet 172.18.0.1/16 brd 172.18.255.255 scope global br-2becce7b1bb4

172.18.0.0     0.0.0.0         255.255.0.0     U     0      0        0 br-2becce7b1bb4

ER:

inet 169.254.251.50/16 brd 169.254.255.255 scope global br-2becce7b1bb4

169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 br-2becce7b1bb4

Container has no access to the network.

Posted: **21 Oct 2022, 04:40**

TerraMaster Support?

Posted: **21 Oct 2022, 18:23**

This issue is being verified.

Posted: **23 Oct 2022, 18:32**

I had the same problems with wrong routes etc. Take a look here:

https://blog.mukmuk.eu/2021/docker-reve ... on-f2-221/

Posted: **23 Oct 2022, 19:00**

{L_BUTTON_AT}mukmuk

I saw it. For me it help only for one run, on the second it resets again.

Posted: **26 Oct 2022, 06:53**

TMSupport wrote: ↑21 Oct 2022, 18:23 This issue is being verified.

Hi! Any updates? It is critical bug for me.

Posted: **31 Oct 2022, 18:21**

This issue has been added to the fix list.

Posted: **16 Dec 2022, 17:02**

TMSupport wrote: ↑31 Oct 2022, 18:21 This issue has been added to the fix list.

Hi! When it will be fixed?

Posted: **16 Dec 2022, 18:18**

Will be fixed in next version.

Posted: **16 Dec 2022, 18:58**

TMSupport wrote: ↑16 Dec 2022, 18:18 Will be fixed in next version.

When will be the next version?

Docker custom network issue