Scheduler service is not started in self-hosted mode

[mikeee]

Expected Behavior

The scheduler should be started when using dapr init.

Actual Behavior

C:\Users\#>dapr init --runtime-version 1.14.0-rc.1
Making the jump to hyperspace...
Container images will be pulled from Docker Hub
Installing runtime version 1.14.0-rc.1
Downloading binaries and setting up components...
Downloaded binaries and completed components set up.
daprd binary has been installed to C:\Users\#\.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

C:\Users\#>docker ps -a
CONTAINER ID   IMAGE                      COMMAND          CREATED         STATUS                     PORTS
                           NAMES
ee713c674604   kindest/node               ""               6 days ago      Exited (0) 292 years ago   80/tcp, 443/tcp, 127.0.0.1:52648->6443/tcp   kind-cluster-control-plane
03a0b3703797   daprio/dapr:1.14.0-rc.1    ""               9 minutes ago   Up 9 minutes               8080/tcp, 9090/tcp, 50005/tcp                dapr_placement
38979748ab7f   openzipkin/zipkin:latest   ""               9 minutes ago   Up 9 minutes               9411/tcp
                           dapr_zipkin
f82bcb0d8866   redis:6                    "redis-server"   9 minutes ago   Up 9 minutes               6379/tcp
                           dapr_redis

C:\Users\#>dapr uninstall --all
Removing Dapr from your machine...
Removing directory: C:\Users\#\.dapr\bin
Removing container: dapr_placement
WARNING: dapr_scheduler container does not exist
Removing container: dapr_redis
Removing container: dapr_zipkin
Removing directory: C:\Users\#\.dapr
Dapr has been removed successfully

Steps to Reproduce the Problem

Mac/Windows - Podman

Release Note

RELEASE NOTE: