Launch system service via cloud-init

Archive RancherOS
1

I’m trying to launch a new system service in system-docker via cloud-init. I am under the impression that I can put a compose yml into a cloud-config file. I am running on EC2, thus all this is passed via the EC2 user-data. The compose yml below when put into the EC2 user-data starts the desired container, but in the user docker, not the system docker. What am I doing wrong, or can this not be achieved this way?

#cloud-config
rightlink:
  restart: always
  net: host
  image: rightscale/rightlink:tve-coreos
  command: "/root/install.sh"
  labels:
    - io.rancher.os.detach=true
    - io.rancher.os.scope=system
    - io.rancher.os.after="cloud-init"
  privileged: true
  volumes_from:
    - command-volumes
    - system-volumes
  volumes:
    - /var/run/dbus:/var/run/dbus
    - /run/systemd:/run/systemd
    - /etc/systemd/system:/etc/systemd/system
  environment:
    - account=1003
2

To answer my own question, the compose yml needs to be nested inside ranher services, e.g.:

#cloud-config
rancher:
  services:
    rightlink:
      restart: always
      net: host
...