Skip to main content

Failed to start Dapr - file does not exist

A short post today; I’ll share an issue a encountered when trying to run a Dapr enabled application. This blog post wouldn’t add much value if I didn’t share a solution as well.

Let me first start by refreshing your memory if you have no clue what Dapr is about. Feel free to skip this intro and move on to the next part if you already tried Dapr before.

Introducing Dapr

image card

On their website, Dapr is described as:

APIs for Building Secure and Reliable Microservices

I don’t think that is the best description, but if you search deeper in the documentation, you find the following description:

Dapr is a portable, event-driven runtime that makes it easy for any developer to build resilient, stateless, and stateful applications that run on the cloud and edge and embraces the diversity of languages and developer frameworks.

That describes it perfectly!

Want to know more? Check out this video:

The issue…

One of the nice features of Dapr is that you can use the Dapr CLI to selfhost and run Dapr on your local development machine.

When I tried to run a Dapr enabled application through Aspire(more about this in a later post), I got the following error:

WARNING: no application command found.

Starting Dapr with id alice. HTTP Port: 59140. gRPC Port: 59139

stderr exec: "C:\\Users\\bawu\\.dapr\\bin\\daprd.exe": file does not exist

The solution…

The solution is easy once you know it. Before you can run a Dapr enabled application on your local machine, you first need to initialize it.

This will:

  • Fetch and install the Dapr sidecar binaries locally.
  • Create a development environment that streamlines application development with Dapr.

So we need to run dapr init:

C:\Users\bawu>dapr init

Making the jump to hyperspace...

Container images will be pulled from Docker Hub

Installing runtime version 1.13.2

Downloading binaries and setting up components...

Downloaded binaries and completed components set up.

daprd binary has been installed to C:\Users\bawu\.dapr\bin.

dapr_placement container is running.

dapr_redis container is running.

dapr_zipkin container is running.

Use `docker ps` to check running containers.

Success! Dapr is up and running. To get started, go here: https://aka.ms/dapr-getting-started

More information

Initialize Dapr in your local environment | Dapr Docs

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more