Docker custom network issue

Discussion about Docker
User avatar
TMRyan
TerraMaster Team
Posts: 817
Joined: 01 Dec 2020, 11:50

Re: Docker custom network issue

Post by TMRyan »

The new version is being tested and will be released if there are no problems.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement)
User avatar
Mizuma
Posts: 7
Joined: 06 Sep 2021, 12:24

Re: Docker custom network issue

Post by Mizuma »

Just installed TOS 5.0 and encountered the same issue. This is critical, entire stacks are impacted.
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18

Re: Docker custom network issue

Post by XFNeo »

TMRyan wrote: 16 Dec 2022, 21:52 The new version is being tested and will be released if there are no problems.
Is it released?
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18

Re: Docker custom network issue

Post by XFNeo »

The problem is still present in the latest TOS version 5.1.31
User avatar
TMnorah
TerraMaster Team
Posts: 117
Joined: 17 Aug 2021, 09:51

Re: Docker custom network issue

Post by TMnorah »

The issue has been fixed, please update the docker application you use. After updating, please refresh your browser cache.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18

Re: Docker custom network issue

Post by XFNeo »

{L_BUTTON_AT}TMnorah
Now I have Docker manager 1.1.80 from 2023-02-06 and TOS 5.1.33
And I have still suffering from this issue
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18

Re: Docker custom network issue

Post by XFNeo »

{L_BUTTON_AT}TMnorah
It is Critical issue! I cant recrate\add containers in this network without additional manipulation with network! When this bug will be fixed?
User avatar
TMzethar
TerraMaster Team
Posts: 1128
Joined: 27 Oct 2020, 16:43

Re: Docker custom network issue

Post by TMzethar »

{L_BUTTON_AT}XFNeo
Both TOS and Docker have new versions. Please update to TOS version 5.1.37 and Docker app version 1.1.98 and try again.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18

Re: Docker custom network issue

Post by XFNeo »

{L_BUTTON_AT}XFNeo
TMzethar wrote: 17 Jun 2023, 12:33 Both TOS and Docker have new versions. Please update to TOS version 5.1.37 and Docker app version 1.1.98 and try again.
Hi! I have the latest Docker version and almost the latests TOS version. I have read the release notes for TOS 5.1.37 - viewtopic.php?f=28&t=4733 and dont see any fixes for docker or network.
Attachments
TOS.png
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18

Re: Docker custom network issue

Post by XFNeo »

{L_BUTTON_AT}XFNeo
TMzethar wrote: 17 Jun 2023, 12:33 Both TOS and Docker have new versions. Please update to TOS version 5.1.37 and Docker app version 1.1.98 and try again.
I have updated TOS to 5.1.40-00005 and Docker app to 1.1.9 and got a new WRONG behaviour: I have 3 custom network: web, nxc_internal, ha_net After reboot TNAS ip address of interface of custom netwok "web" changed 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
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.18.0.0      0.0.0.0         255.255.0.0     U     0      0        0 nxc_internal
172.19.0.0      0.0.0.0         255.255.0.0     U     0      0        0 ha_net
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

Code: Select all

#ip a
...
13: web: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:8e:b1:9d:ba brd ff:ff:ff:ff:ff:ff
    inet 169.254.251.144/16 brd 169.254.255.255 scope global web
       valid_lft forever preferred_lft forever
    inet6 fe80::42:8eff:feb1:9dba/64 scope link
       valid_lft forever preferred_lft forever
14: ha_net: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:ef:70:f5:7f brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 brd 172.19.255.255 scope global ha_net
       valid_lft forever preferred_lft forever
    inet6 fe80::42:efff:fe70:f57f/64 scope link
       valid_lft forever preferred_lft forever
15: nxc_internal: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:a1:ae:01:a5 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global nxc_internal
       valid_lft forever preferred_lft forever
    inet6 fe80::42:a1ff:feae:1a5/64 scope link
       valid_lft forever preferred_lft forever
 ...

Code: Select all

# docker network inspect web
[
    {
        "Name": "web",
        "Id": "ee6361becc4cc0b73eabc48cfa90c89b4e2dd23d6efbf0d43d86ba2e93d2b24e",
        "Created": "2022-10-18T23:09:49.898501577+04:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "172.23.0.0/16",
                    "Gateway": "172.23.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "0b045aaf9b162adca7d48ef72a7ef64852154b1cfb5d6f014b477c4fb040bf41": {
                "Name": "container-reload",
                "EndpointID": "0fc4587c32d3183aff1053969398042b3508ecfe9f5f835f1167b07d96f9e28a",
                "MacAddress": "02:42:ac:17:00:02",
                "IPv4Address": "172.23.0.2/16",
                "IPv6Address": ""
            },
            "6b1bbde6712de2c5d1cd9511b9f1abfe775ace01eeb667d8142a7531203a3835": {
                "Name": "nginx",
                "EndpointID": "106f26a5a5258865e7528465308e27d02243350a1b60b2bd418785bb1464b6b4",
                "MacAddress": "02:42:ac:17:00:04",
                "IPv4Address": "172.23.0.4/16",
                "IPv6Address": ""
            },
            "76b2b229630b10bee24dd9b202c6362d8cbc054c3b2e8157ff5de285625a9ad2": {
                "Name": "forex-cache-697098a8",
                "EndpointID": "ec2b91c64e14976a0eae189ebc90e554da027f287626f40215e9ef017e79c8f7",
                "MacAddress": "02:42:ac:17:00:03",
                "IPv4Address": "172.23.0.3/16",
                "IPv6Address": ""
            },
            "ee2021bd86e30a8b59880d18fd16135753dd0c494ae83c43e7882077e7501efb": {
                "Name": "my-app-1",
                "EndpointID": "d920c8be424c65bc2f3afb6f04b755075e2eb0d4cdbcbc20cbc9689eac8741e5",
                "MacAddress": "02:42:ac:17:00:05",
                "IPv4Address": "172.23.0.5/16",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.bridge.name": "web"
        },
        "Labels": {}
    }
]
When will you fix network problem with docker?
Locked