Swarm: No key to tell if --data-path-addr was used

[praving55]

Description
Swarm: No key to tell if --data-path-addr was used

Steps to reproduce the issue:

1. Initialize a new swarm

docker swarm init --advertise-addr=192.168.0.1 --data-path-addr=192.168.0.2

2. Inspect the node

docker node inspect self

Describe the results you received:
I got all node properties except the one set by --data-path-addr.

Describe the results you expected:
Apart from --advertise-addr, --data-path-addr should have been present as well.

  },
        "Status": {
            "State": "ready",
            "Addr": "192.168.0.1"
        },
        "ManagerStatus": {
            "Leader": true,
            "Reachability": "reachable",
            "Addr": "192.168.0.1:2377"
        }

Output of docker version:

docker version
Client:
 Version:      17.06.0-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:20:36 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.0-ce
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:21:56 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:

docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 11
Server Version: 17.06.0-ce
Storage Driver: devicemapper
 Pool Name: docker-253:0-67374335-pool
 Pool Blocksize: 65.54kB
 Base Device Size: 10.74GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 1.027GB
 Data Space Total: 107.4GB
 Data Space Available: 48.66GB
 Metadata Space Used: 1.704MB
 Metadata Space Total: 2.147GB
 Metadata Space Available: 2.146GB
 Thin Pool Minimum Free Space: 10.74GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.135-RHEL7 (2016-11-16)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
 NodeID: m22q0ey5zf87ei88977dvlxyc
 Is Manager: true
 ClusterID: qrbptib70uqhs4gfhitb675ty
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Root Rotation In Progress: false
 Node Address: 192.168.0.1
 Manager Addresses:
  192.168.0.1:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-327.36.3.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 7.64GiB
Name: localhost.localdomain
ID: 4XCJ:T2FS:4JJA:FMEN:QAG7:NQX2:UKBS:NKEB:I5DR:IMX3:ULXK:FZAF
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: psg5
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: devicemapper: usage of loopback devices is strongly discouraged for production use.
         Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
WARNING: bridge-nf-call-ip6tables is disabled

[farnasirim]

@thaJeztah DataPathAddr is not included swarmkit's Node proto. I'm actually interested in doing this. Should I head over to swarmkit first?

[schildbach]

Actually I've just used netstat -lnptu | grep 4789 to verify --data-path-addr wg0 is actually picked up by docker swarm init.

But guess what, it seems to be ignored:

# netstat -lnptu | grep 4789
udp        0      0 0.0.0.0:4789            0.0.0.0:*                           - 

I also tried the IP of my interface, didn't work either. --listen-addr wg0 works fine as it should however.

Is this a bug?