Restarting Docker service in Swarm mode causes network interruption?

Archive Windows Server 2016
1

Expected behavior

No disruption with any network activities

Actual behavior

Couple ping lost

Information

Docker info

Server Version: 18.09.0
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gelf json-file local logentries splunk syslog
Swarm: active
NodeID: 84b6kw96iypgwwmxjtpl4jtzg
Is Manager: true
ClusterID: p4nwey7l73dhtm5rkibkjv0hq
Managers: 1
Nodes: 1
Default Address Pool: 10.0.0.0/8
SubnetSize: 24
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

I tried with bridge=none and not and got the same behavior.

C:\WINDOWS\system32>docker network ls
NETWORK ID NAME DRIVER SCOPE
104f4d9f1d33 nat nat local
3b40b4e7d8b3 none null local

Steps to reproduce the behavior

  1. [Swarm Host] Initialize docker swarm
  2. [Host A] Run “ping -t [Swarm Host]”
  3. [Swarm Host] Restart docker service
  4. [Host A] Request timed out.

Is this expected?
I followed the instructions from Microsoft to setup the windows server and docker.