overlay doesn't work on centos 7

[Fangfenghua]

[root@localhost sysconfig]# uname -a
Linux localhost.localdomain 3.10.0-327.13.1.el7.x86_64 #1 SMP Thu Mar 31 16:04:38 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[root@localhost sysconfig]# docker -v
Docker version 1.10.3, build 20f81dd

[root@localhost sysconfig]# docker -v
Docker version 1.10.3, build 20f81dd
[root@localhost sysconfig]# docker info
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 1
Server Version: 1.10.3
Storage Driver: devicemapper
Pool Name: docker-253:0-121088-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 24.38 MB
Data Space Total: 107.4 GB
Data Space Available: 42.68 GB
Metadata Space Used: 598 kB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.147 GB
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
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev or use --storage-opt dm.no_warn_on_loop_devices=true to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.107-RHEL7 (2015-12-01)
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: overlay host bridge null
Kernel Version: 3.10.0-327.13.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.793 GiB
Name: localhost.localdomain
ID: FAB4:OOKH:TZUX:UEIY:2SUV:2MWU:MOZD:HH7F:3U43:5WNX:FGLI:TGNV
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Cluster store: etcd://127.0.0.1:2379
Cluster advertise: 192.168.2.67:2181

I create a overlay network,then create two container attach to it.I found contaner in different host,cant ping each other. so i want to debug it.

i excetue:
ln -s /var/run/docker/netns /var/run

then:
[root@localhost sysconfig]# ip net ls
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
aa92ed573ae6
RTNETLINK answers: Invalid argument
4-6299a18ded
[root@localhost sysconfig]#

when i debug the network, i found i cant access the network namespace

[chenchun]

@Fangfenghua Can you paste the result of netstat -apn | grep '4789\|8472', bridge fdb show | grep vx and ip neigh show | grep vx on each node after starting two containers attaching to the overlay network?

[Fangfenghua]

@chenchun change storage driver from devicemapper loog to lvm-derect the problem sloved. but i don't konw why