Unable to deploy dapr application using Dockerfile

Expected Behavior

Successfully able to deploy and run the container

Actual Behavior

Container is unable to start and generating the below logs:

Events:
Type Reason Age From Message

Normal Scheduled 29s default-scheduler Successfully assigned dapr-system/currency-exchange-6c4fdcbb88-wh9mp to gke-k8s-poc-istio-default-pool-35bfdde6-m30w
Normal Pulled 28s kubelet, gke-k8s-poc-istio-default-pool-35bfdde6-m30w Successfully pulled image "naichowdhury/daprcurrencyexchange:0.0.2" in 508.1759ms
Normal Pulled 27s kubelet, gke-k8s-poc-istio-default-pool-35bfdde6-m30w Successfully pulled image "naichowdhury/daprcurrencyexchange:0.0.2" in 516.241312ms
Normal Pulling 12s (x3 over 28s) kubelet, gke-k8s-poc-istio-default-pool-35bfdde6-m30w Pulling image "naichowdhury/daprcurrencyexchange:0.0.2"
Normal Created 12s (x3 over 28s) kubelet, gke-k8s-poc-istio-default-pool-35bfdde6-m30w Created container currency-exchange
Normal Pulled 12s kubelet, gke-k8s-poc-istio-default-pool-35bfdde6-m30w Successfully pulled image "naichowdhury/daprcurrencyexchange:0.0.2" in 509.781022ms
Warning Failed 11s (x3 over 28s) kubelet, gke-k8s-poc-istio-default-pool-35bfdde6-m30w Error: failed to start container "currency-exchange": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: "dapr": executable file not found in $PATH": unknown
Warning BackOff 7s (x3 over 26s) kubelet, gke-k8s-poc-istio-default-pool-35bfdde6-m30w Back-off restarting failed container

Steps to Reproduce the Problem

Using the attached docker file and deployment file to deploy my application in my GKE cluster where already dapr is installed:

Dockerfile.txt
deployment.txt

Note:

Have installed dapr in both the remote machine and my local machine (since am using the google cloud sdk shell to run the deployment files from my local)

Read the attached Dockerfile.txt and deployment.txt first, then reproduce the deployment in the stated GKE environment and inspect how the container is started. Compare the startup command with the available executables and verify that the deployed container starts successfully without the reported missing-dapr error.