failed to create endpoint on network tes23 because network id not found

I use two nodes to build overlay network. One node can inspect/connect/disconnect overlay well, but the other one can only inspect network's info , When I try to connect an container to this network:
It fails for :

kiongf@youruncloud:~/k8s/project$ sudo docker run -d --net=tes23 busybox sleep 1000
ba0a0064f1de046f8b25dfe67c6bad2b22f3f972cfa49a49bcbf0b0cfd006c7d
docker: Error response from daemon: failed to create endpoint backstabbing_archimedes on network tes23: network id "50a3fcedfe64b4834564743ddb43e03ee12409c002ce3aa6444dacbfc4bfa300" not found.

I can inspect this network on this node :

kiongf@youruncloud:~/k8s/project$ docker network inspect tes23
WARNING: Error loading config file:/home/kiongf/.docker/config.json - stat /home/kiongf/.docker/config.json: permission denied
[
{
"Name": "tes23",
"Id": "50a3fcedfe64b4834564743ddb43e03ee12409c002ce3aa6444dacbfc4bfa300",
"Scope": "global",
"Driver": "overlay",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": null,
"Config": [
{
"Subnet": "10.12.0.0/16"
}
]
},

This is my docker info :

kiongf@youruncloud:~/k8s/project$ docker info
WARNING: Error loading config file:/home/kiongf/.docker/config.json - stat /home/kiongf/.docker/config.json: permission denied
Containers: 11
Running: 0
Paused: 0
Stopped: 11
Images: 91
Server Version: 1.11.2
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 162
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: overlay bridge null host
Kernel Version: 4.4.0-34-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.756 GiB
Name: youruncloud
ID: JX2L:QY7S:7GTK:QOGL:Y6PM:JIXV:4OI6:CYGK:JYBV:SO5P:CDQR:YIMS
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): true
File Descriptors: 17
Goroutines: 57
System Time: 2016-08-18T09:33:24.213378763+08:00
EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Cluster store: etcd://192.168.4.11:2379
Cluster advertise: 192.168.4.11:2376

Start with the reported docker run --net=tes23 failure and compare it with docker network inspect on both overlay-network nodes. Review the overlay network and cluster-store behavior shown by docker info, including the etcd configuration, to determine why the network ID is visible but unavailable when creating the endpoint. Done means the container connects successfully on both nodes without the network-id-not-found error.