TerraMaster Forum

Posted: **03 Aug 2023, 19:21**

{L_BUTTON_AT}XFNeo

If you want to add domain name resolution, you can try to add ip and domain name in the /etc/hosts file of the container.

Posted: **04 Aug 2023, 15:52**

{L_BUTTON_AT}Bipe

Stop writing about domain name resolution in this thread!
This thread about problem with ip address in custom docker networks!

Posted: **04 Aug 2023, 15:56**

{L_BUTTON_AT}TMzethar

Please read MY first message in this thread and this one viewtopic.php?f=43&t=3817&start=10#p28608 The problem was not fixed on the latest TOS version with the latest docker app.

Posted: **04 Aug 2023, 16:26**

{L_BUTTON_AT}XFNeo

We confirmed that the problem has been fixed and no similar cases have been found.
Please create a new custom network to see if the IP is still modified? Maybe the configuration created before has never worked.
If you still have the problem after you try to create a new custom network, we would like to know why you still encounter the problem. We suggest that you contact the technical support team, and we can arrange an engineer to check the specific reason remotely.

Posted: **04 Aug 2023, 16:33**

{L_BUTTON_AT}TMzethar

Ok, I will create a new new custom network and check.

Posted: **07 Aug 2023, 00:41**

@XFNeo Were you able to solve this? I am having the same issue. Before this last update I had to adjust the route for my custom network every time after bringing it up, as described by @mukmuk, but at least it worked after doing that.

I also share your frustration as I read this thread and saw some of the responses

Posted: **07 Aug 2023, 00:48**

{L_BUTTON_AT}XFNeo

Sorry I did not correctly tag XFNeo or mukmuk

Posted: **09 Aug 2023, 21:14**

{L_BUTTON_AT}Senkrad

Thanks) Can you try to create a new custom network and check with it as @TMzethar recommended, because I dont know when I cna check it, now I'm away from TNAS? But be sure that you have the latest Docker app and TNAS OS versions.

[at=TMzethar post_id=28865 time=1691137565 user_id=2405]
We confirmed that the problem has been fixed and no similar cases have been found.
Please create a new custom network to see if the IP is still modified? Maybe the configuration created before has never worked.
If you still have the problem after you try to create a new custom network, we would like to know why you still encounter the problem. We suggest that you contact the technical support team, and we can arrange an engineer to check the specific reason remotely.
[/at]

Posted: **25 Aug 2023, 19:52**

{L_BUTTON_AT}TMzethar

The problem was not resloved! I have delete all containers and custom networks. Update docker manager to the latest version 1.2.3 Reboot TNAS Create a custom network "web"

Code: Select all

docker network create --opt com.docker.network.bridge.name=web web

Code: Select all

[
    {
        "Name": "web",
        "Id": "c9a5d595771ce593494171b0a83502213ff9f3f112e84b6f9a42f444b3e8fe6b",
        "Created": "2023-08-25T15:14:15.395948203+04:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "172.18.0.0/16",
                    "Gateway": "172.18.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {
            "com.docker.network.bridge.name": "web"
        },
        "Labels": {}
    }
]

ifconfig showed the right ip 172.18.0.1/16 on this interface I upped my docker-compose bundles with additional custom networks "ha_net" and "nxc_internal" 1st:

Code: Select all

....
networks:
  web:
    external: true
  ha_net:
    internal: false
    driver_opts:
      com.docker.network.bridge.name: ha_net

2nd:

Code: Select all

....
networks:
  web:
    external: true
  internal:
    internal: true
    driver_opts:
      com.docker.network.bridge.name: nxc_internal

And network addresses were reseted AGAIN to 169.254.0.0!

Code: Select all

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 web
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 ha_net
172.10.11.0     172.10.11.2     255.255.255.0   UG    0      0        0 tun0
172.10.11.2     0.0.0.0         255.255.255.255 UH    0      0        0 tun0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.19.0.0      0.0.0.0         255.255.0.0     U     0      0        0 nxc_internal
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

You can not fix this f**king bug since 18 Oct 2022

Posted: **06 Sep 2023, 19:14**

{L_BUTTON_AT}XFNeo

hello，It is recommended that you use docker's default bridge interface name when creating a network,like starting with "br-", and do not use the "docker network create --opt" parameter.

CODE: SELECT ALL
docker network create --opt com.docker.network.bridge.name=web web

change like :
docker network create web

TerraMaster Forum

Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue

Re: Docker custom network issue