The documentation you are viewing is for Dapr v1.6 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Initialize Dapr in your local environment
Now that you’ve installed the Dapr CLI, use the CLI to initialize Dapr on your local machine.
Dapr runs as a sidecar alongside your application. In self-hosted mode, this means it is a process on your local machine. By initializing Dapr, you:
- Fetch and install the Dapr sidecar binaries locally.
- Create a development environment that streamlines application development with Dapr.
Dapr initialization includes:
- Running a Redis container instance to be used as a local state store and message broker.
- Running a Zipkin container instance for observability.
- Creating a default components folder with component definitions for the above.
- Running a Dapr placement service container instance for local actor support.
DockerThe recommended development environment requires Docker. While you can initialize Dapr without a dependency on Docker), the next steps in this guide assume the recommended Docker development environment.
Step 1: Open an elevated terminal
You will need to use
sudo for this quickstart if:
- You run your Docker commands with
- The install path is
/usr/local/bin(default install path).
Run Windows Terminal or command prompt as administrator.
- Right click on the Windows Terminal or command prompt icon.
- Select Run as administrator.
Step 2: Run the init CLI command
Install the latest Dapr runtime binaries:
Step 3: Verify Dapr version
CLI version: 1.6.0
Runtime version: 1.6.1
Step 4: Verify containers are running
As mentioned earlier, the
dapr init command launches several containers that will help you get started with Dapr. Verify you have container instances with
redis images running:
Step 5: Verify components directory has been initialized
dapr init, the CLI also creates a default components folder that contains several YAML files with definitions for a state store, Pub/sub, and Zipkin. The Dapr sidecar will read these components and use:
- The Redis container for state management and messaging.
- The Zipkin container for collecting traces.
Verify by opening your components directory:
- On Windows, under
- On Linux/MacOS, under
bin components config.yaml
Next step: Use the Dapr API >>
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.