Re-creating the ingress swarm network fails to create the "Containers" and "Peers" in the ingress network configuration

[aki-k]

Description

Re-creating the ingress swarm network fails to create the "Containers" and "Peers" in the ingress network configuration

Steps to reproduce the issue:

1. docker swarm init --listen-addr eth1:2377 --advertise-addr eth1:2377
2. docker network rm ingress
3. docker network create --driver overlay --ingress --subnet 10.0.1.0/24 --gateway 10.0.1.1 --scope swarm ingress
4. docker network inspect ingress

Describe the results you received:

"Containers" and "Peers" that the docker swarm init step created in the ingress network configuration go missing after re-creating the ingress network with docker network create.

Describe the results you expected:

I would have expected the docker network create process create a similar configuration for the ingress network than what the docker swarm init did.

Additional information you deem important (e.g. issue happens only occasionally):

This is the missing configuration that doesn't appear after docker network create:

        "Containers": {
            "ingress-sbox": {
                "Name": "ingress-endpoint",
                "EndpointID": "49bf4e0368f59d69493068a070eaa8a1a779f7ee04034141b7425d4a4647e340",
                "MacAddress": "02:42:0a:ff:00:02",
                "IPv4Address": "10.255.0.2/16",
                "IPv6Address": ""
            }
        },

        "Peers": [
            {
                "Name": "0522518ea97c",
                "IP": "10.0.0.1"
            }
        ]

10.0.0.1 is the IP address of my eth1 interface.

Output of docker version:

Client: Docker Engine - Community
 Version:           19.03.3
 API version:       1.40
 Go version:        go1.12.10
 Git commit:        a872fc2f86
 Built:             Tue Oct  8 00:58:10 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.3
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.10
  Git commit:       a872fc2f86
  Built:            Tue Oct  8 00:56:46 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 oci-add-hooks:
  Version:          
  GitCommit:        oci-add-hooks-b25d3bd0678c9812f7bdd6807209dbb89145a1cd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker info:

Client:
 Debug Mode: false

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 19.03.3
 Storage Driver: btrfs
  Build Version: Btrfs v4.9.1
  Library Version: 102
 Logging Driver: json-file
 Cgroup Driver: systemd
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: active
  NodeID: 71hmz9554cia44g27oue5rd37
  Is Manager: true
  ClusterID: yonbxh7sipfiwqxwghm5z532j
  Managers: 1
  Nodes: 1
  Default Address Pool: 10.0.0.0/8  
  SubnetSize: 24
  Data Path Port: 4789
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: 10.0.0.1
  Manager Addresses:
   10.0.0.1:2377
 Runtimes: oci-add-hooks runc
 Default Runtime: oci-add-hooks
 Init Binary: docker-init
 containerd version: b34a5c8af56e510852c35414db4c1f4fa6172339
 runc version: oci-add-hooks-b25d3bd0678c9812f7bdd6807209dbb89145a1cd
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
  selinux
  userns
 Kernel Version: 5.2.14-1.el7.elrepo.x86_64
 Operating System: CentOS Linux 7 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.852GiB
 Name: hostname
 ID: 4SAO:QMLO:TBSL:I4VJ:RWAZ:TJXH:V4NK:XPCE:A5EH:LIMZ:4CSY:LIX3
 Docker Root Dir: /var/lib/docker/262144.262144
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):

I'm running the VMs in an IaaS cloud.

[aki-k]

After joining two other VMs to the swarm, the ingress network configuration on the second and third VM include those "Containers" and "Peers" keys , but the "Peers" configuration is missing the swarm master IP address information.

Also the first swarm manager node's ingress network configuration is missing both the "Containers" and "Peers" keys after expanding the swarm.

[geek-at]

did you ever find a solution @aki-k ?

I'm having the same problem. My nodes all show up but my manager node has only itself as peer while all others have each other

[aki-k]

@geek-at

Sorry I didn't find a solution for that.