rke: /opt/rke/entrypoint.sh: no such file or directory

RKE version: rke version v0.1.9-rc9 rke-tools version 0.1.13, forked with a minor change to permissions that I’m testing for the cloud-provider.sh file. I’ve uploaded this to a private registry as tag:

privateregistry.azurecr.io/rancher/rke-tools:v0.1.14

Operating system and kernel: (cat /etc/os-release, uname -r preferred) CoreOS

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) Azure

cluster.yml file: Kubernetes version: Default (rancher/hyperkube:v1.11.1-rancher1)

system_images:
  alpine: privateregistry.azurecr.io/rancher/rke-tools:v0.1.14
  nginx_proxy: privateregistry.azurecr.io/rancher/rke-tools:v0.1.14
  cert_downloader: privateregistry.azurecr.io/rancher/rke-tools:v0.1.14
  kubernetes_services_sidecar: privateregistry.azurecr.io/rancher/rke-tools:v0.1.14

Steps to Reproduce:

rke up --disable-port-check

Results:

FATA[0141] [controlPlane] Failed to bring up Control Plane:
  Failed to start [kube-apiserver] container on host [10.18.160.21]:
  Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247:
  starting container process caused \"exec: \\\"/opt/rke/entrypoint.sh\\\":
  stat /opt/rke/entrypoint.sh: no such file or directory\"\n" 

This should have hit /opt/rke-tools/entrypoint.sh