dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Docs for `--scheduler-override-broadcast-host-port` 

Signed-off-by: Albert Callarisa <albert@diagrid.io>
This commit is contained in:
Albert Callarisa 2025-07-14 07:30:14 +02:00
parent 8f633fea4a
commit 14bbb87159
No known key found for this signature in database
GPG Key ID: 450F38BCAA761685
1 changed files with 17 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
daprdocs/content/en/reference/cli/dapr-init.md
View File

@ -46,6 +46,7 @@ dapr init [flags]
| `--container-runtime` | | `docker` | Used to pass in a different container runtime other than Docker. Supported container runtimes are: `docker`, `podman` | | `--container-runtime` | | `docker` | Used to pass in a different container runtime other than Docker. Supported container runtimes are: `docker`, `podman` |
| `--dev` | | | Creates Redis and Zipkin deployments when run in Kubernetes. | | `--dev` | | | Creates Redis and Zipkin deployments when run in Kubernetes. |
| `--scheduler-volume` | | | Self-hosted only. Optionally, you can specify a volume for the scheduler service data directory. By default, without this flag, scheduler data is not persisted and not resilient to restarts. | | `--scheduler-volume` | | | Self-hosted only. Optionally, you can specify a volume for the scheduler service data directory. By default, without this flag, scheduler data is not persisted and not resilient to restarts. |
| `--scheduler-override-broadcast-host-port` | | | Self-hosted only. Specify the scheduler broadcast host and port, for example: 192.168.42.42:50006. If not specified, it uses localhost:50006 (6060 for Windows). |
### Examples ### Examples
@ -70,7 +71,7 @@ Dapr can also run [Slim self-hosted mode]({{< ref self-hosted-no-docker.md >}}),
dapr init -s dapr init -s
``` ```
> To switch to Dapr Github container registry as the default registry, set the `DAPR_DEFAULT_IMAGE_REGISTRY` environment variable value to be `GHCR`. To switch back to Docker Hub as default registry, unset this environment variable. > To switch to Dapr Github container registry as the default registry, set the `DAPR_DEFAULT_IMAGE_REGISTRY` environment variable value to be `GHCR`. To switch back to Docker Hub as default registry, unset this environment variable.
**Specify a runtime version** **Specify a runtime version**
@ -148,7 +149,7 @@ dapr init --network mynet
Verify all containers are running in the specified network. Verify all containers are running in the specified network.
```bash ```bash
docker ps docker ps
``` ```
Uninstall Dapr from that Docker network. Uninstall Dapr from that Docker network.
@ -157,6 +158,18 @@ Uninstall Dapr from that Docker network.
dapr uninstall --all --network mynet dapr uninstall --all --network mynet
``` ```
**Specify scheduler broadcast host and port**
You can specify the scheduler broadcast host and port, for example: 192.168.42.42:50006.
This is necessary when you have to connect to the scheduler using a different host and port, as the scheduler only allows connections matching this host and port.
By default, the scheduler will use localhost:50006 (6060 for Windows), as it's the most common way to connect to the scheduler.
```bash
dapr init --scheduler-override-broadcast-host-port 192.168.42.42:50006
```
{{% /codetab %}} {{% /codetab %}}
{{% codetab %}} {{% codetab %}}
@ -192,11 +205,11 @@ dapr init -k --set global.tag=1.0.0 --set dapr_operator.logLevel=error
You can also specify a private registry to pull container images from. As of now `dapr init -k` does not use specific images for sentry, operator, placement, scheduler, and sidecar. It relies on only Dapr runtime container image `dapr` for all these images. You can also specify a private registry to pull container images from. As of now `dapr init -k` does not use specific images for sentry, operator, placement, scheduler, and sidecar. It relies on only Dapr runtime container image `dapr` for all these images.
Scenario 1 : dapr image hosted directly under root folder in private registry - Scenario 1 : dapr image hosted directly under root folder in private registry -
```bash ```bash
dapr init -k --image-registry docker.io/username dapr init -k --image-registry docker.io/username
``` ```
Scenario 2 : dapr image hosted under a new/different directory in private registry - Scenario 2 : dapr image hosted under a new/different directory in private registry -
```bash ```bash
dapr init -k --image-registry docker.io/username/<directory-name> dapr init -k --image-registry docker.io/username/<directory-name>
``` ```