Prevent scheduling scaled containers on same host

Archive Rancher 1.x
1

Given http://docs.rancher.com/rancher/concepts/scheduling/ it appears the default behavior is to prefer (but not require) to not have containers of the same Service scheduled to the same host.

Is there a way to require containers are not scheduled to the same host? In the case that you have volumes based on local paths, it seems important for service containers to not share the same local files in some cases (e.g. databases etc).

2

Believe I figured out a way to do this e.g:

docker-compose:

es4:
  labels:
    es4: 'true'
    io.rancher.scheduler.affinity:container_label_ne: es4=true
  tty: true
  image: elasticsearch
  volumes:
  - /data/es-demo4:/data/es-demo4
  stdin_open: true

Note the label es4=true and the scheduling requirement that there must not be another container with the label es4=true.