How to force fleet to run units on different machines after cluster start?

Question

Docker

Good afternoon!
Colleagues tell me.
I have a cluster of 3 machines with COREOS (766.3), built a static etcd2 cluster.

[email protected] ~ $ etcdctl member list
2e1647e0d9007562: name=core03 peerURLs=https://10.0.0.4:2380 clientURLs=https://10.0.0.4:2379
6e85486869bf8dd7: name=core05 peerURLs=https://10.0.0.6:2380 clientURLs=https://10.0.0.6:2379
a15535ec55f4a2cd: name=core04 peerURLs=https://10.0.0.5:2380 clientURLs=https://10.0.0.5:2379

Also launched fleet.

[email protected] ~ $ fleetctl list-machines
MACHINE         IP              METADATA
80afd831...     192.168.113.39  -
883b300a...     192.168.113.40  -
c9a1d59d...     192.168.113.38  -

The question is how to make the units run on different machines in the cluster at startup.
Now after the start of the cluster, all units are launched on the 2nd machine (loaded in order)

[email protected] ~ $ fleetctl list-units
UNIT                    MACHINE                         ACTIVE  SUB
docker-ca.service       80afd831.../192.168.113.39      active  running
docker-dns.service      80afd831.../192.168.113.39      active  running
docker-ftp.service      80afd831.../192.168.113.39      active  running
docker-ntp.service      80afd831.../192.168.113.39      active  running
docker-registry.service 80afd831.../192.168.113.39      active  running
docker-rsyslog.service  80afd831.../192.168.113.39      active  running