Run Dapr in self-hosted mode on Dapr Docs

Overview of Dapr in self-hosted mode

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Dapr can be configured to run in self-hosted mode on your local developer machine or on production VMs. Each running service has a Dapr runtime process (or sidecar) which is configured to use state stores, pub/sub, binding components and the other building blocks.

Initialization

Dapr can be initialized with Docker (default) or in slim-init mode. It can also be initialized and run in offline or airgap environments.

Note

You can also use Podman in place of Docker as container runtime. Please refer dapr init with Podman for more details. It can be useful in the scenarios where docker cannot be installed due to various networking constraints.

The default Docker setup provides out of the box functionality with the following containers and configuration:

How-To: Run Dapr in self-hosted mode with Docker

Mon, 01 Jan 0001 00:00:00 +0000

This article provides guidance on running Dapr with Docker on a Windows/Linux/macOS machine or VM.

Prerequisites

Initialize Dapr environment

To initialize the Dapr control plane containers and create a default configuration file, run:

dapr init

Run both app and sidecar as a process

The dapr run CLI command can be used to launch a Dapr sidecar along with your application:

dapr run --app-id myapp --app-port 5000 -- dotnet run

This command will launch both the daprd sidecar binary and run dotnet run, launching your application.

How-To: Run Dapr in self-hosted mode with Podman

Mon, 01 Jan 0001 00:00:00 +0000

This article provides guidance on running Dapr with Podman on a Windows/Linux/macOS machine or VM.

Prerequisites

Initialize Dapr environment

To initialize the Dapr control plane containers and create a default configuration file, run:

dapr init --container-runtime podman

Run both app and sidecar as a process

The dapr run CLI command can be used to launch a Dapr sidecar along with your application:

dapr run --app-id myapp --app-port 5000 -- dotnet run

This command launches both the daprd sidecar and your application.

How-To: Run Dapr in an offline or airgap environment

Mon, 01 Jan 0001 00:00:00 +0000

Overview

By default, Dapr initialization downloads binaries and pulls images from the network to setup the development environment. However, Dapr also supports offline or airgap installation using pre-downloaded artifacts, either with a Docker or slim environment. The artifacts for each Dapr release are built into a Dapr Installer Bundle which can be downloaded. By using this installer bundle with the Dapr CLI init command, you can install Dapr into environments that do not have any network access.

How-To: Run Dapr in self-hosted mode without Docker

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

Install the Dapr CLI

Initialize Dapr without containers

The Dapr CLI provides an option to initialize Dapr using slim init, without the default creation of a development environment with a dependency on Docker. To initialize Dapr with slim init, after installing the Dapr CLI, use the following command:

dapr init --slim

Two different binaries are installed:

daprd
placement

The placement binary is needed to enable actors in a Dapr self-hosted installation.

How-to: Persist Scheduler Jobs

Mon, 01 Jan 0001 00:00:00 +0000

The Scheduler service is responsible for writing jobs to its Etcd database and scheduling them for execution. By default, the Scheduler service database writes this data to the local volume dapr_scheduler, meaning that this data is persisted across restarts.

The host file location for this local volume is typically located at either /var/lib/docker/volumes/dapr_scheduler/_data or ~/.local/share/containers/storage/volumes/dapr_scheduler/_data, depending on your container runtime. Note that if you are using Docker Desktop, this volume is located in the Docker Desktop VM’s filesystem, which can be accessed using:

Steps to upgrade Dapr in a self-hosted environment

Mon, 01 Jan 0001 00:00:00 +0000

Uninstall the current Dapr deployment:

Note
This will remove the default $HOME/.dapr directory, binaries and all containers (dapr_redis, dapr_placement and dapr_zipkin). Linux users need to run sudo if docker command needs sudo.
```
dapr uninstall --all
```
Download and install the latest CLI by visiting this guide.
Initialize the Dapr runtime:
```
dapr init
```
Ensure you are using the latest version of Dapr (v1.16.9)) with:
```
$ dapr --version

CLI version: 1.16
Runtime version: 1.16
```

Uninstall Dapr in a self-hosted environment

Mon, 01 Jan 0001 00:00:00 +0000

The following CLI command removes the Dapr sidecar binaries and the placement container:

dapr uninstall

The above command will not remove the Redis or Zipkin containers that were installed during dapr init by default, just in case you were using them for other purposes. To remove Redis, Zipkin, Actor Placement container, as well as the default Dapr directory located at $HOME/.dapr or %USERPROFILE%\.dapr\, run:

dapr uninstall --all

Note

For Linux/MacOS users, if you run your docker cmds with sudo or the install path is /usr/local/bin(default install path), you need to use sudo dapr uninstall to remove dapr binaries and/or the containers.