# What dictates the image that is used for the Drone controller job in kubernetes **URL:** \ **Category:** Drone Support\ **Created:** [January 4, 2019, 4:52pm UTC](https://drone.discourse.group/t/what-dictates-the-image-that-is-used-for-the-drone-controller-job-in-kubernetes/9131 "2019-01-04T16:52:29Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![glycerine102](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/glycerine102/32/4705_2.png) [@glycerine102](https://drone.discourse.group/u/glycerine102)\ **Post date:** [January 4, 2019, 4:52pm UTC](https://drone.discourse.group/t/what-dictates-the-image-that-is-used-for-the-drone-controller-job-in-kubernetes/9131/1 "2019-01-04T16:52:29Z")
I am running a Kubernetes ARM cluster but the job spawned starts pulling down a drone/controller image and is attempting to use the `linux-amd64` tag. ```auto Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 16s default-scheduler Successfully assigned builds/drone-job-68rvz-425vq to kube2 Normal Pulling 13s kubelet, kube2 pulling image "drone/controller:linux-amd64" Normal Pulled 12s kubelet, kube2 Successfully pulled image "drone/controller:linux-amd64" Normal Created 11s kubelet, kube2 Created container Normal Started 10s kubelet, kube2 Started container ``` ```auto kubectl logs drone-job-68rvz-425vq standard_init_linux.go:190: exec user process caused "exec format error" ``` The drone server deployment is using `drone/drone:1.0.0-rc.3` in the arm cluster. ```auto ❯ kubectl exec drone-deploy-bbd8848b5-w9rqn -- cat /proc/cpuinfo | grep -m 1 'model name' model name : ARMv7 Processor rev 4 (v7l) ``` I see `drone/controller:1.0.0-rc.3-linux-arm` exists, but how do I tell my Drone server deployment to spawn jobs from it? I don’t see any new environment variables for this. --- _[View the full topic](https://drone.discourse.group/t/what-dictates-the-image-that-is-used-for-the-drone-controller-job-in-kubernetes/9131)._