Expected Behavior
I would like to open a terminal window, and using the installed Dapr CLI run dapr init and see:
Making the jump to hyperspace...
Container images will be pulled from Docker Hub
Installing runtime version 1.17.3
Downloading binaries and setting up components...
Downloaded binaries and completed components set up.
daprd binary has been installed to C:.dapr\bin
dapr_placement container is running.
dapr_redis container is running.
dapr_zipkin container is running.
dapr_scheduler container is running.
Use docker ps to check running containers.
Success! Dapr is up and running. To get started, go here: https://docs.dapr.io/getting-started
Actual Behavior
_> dapr init
Making the jump to hyperspace...
Container images will be pulled from Docker Hub
Installing runtime version 1.17.3
Downloading binaries and setting up components...
docker: Error response from daemon: failed to set up container networking: driver failed programming external > connectivity on endpoint dapr_scheduler (2df4827069b7bcc5efaa303b3e394c019a94a8176754bc63d49a0d471295e95b): failed to bind host port for 0.0.0.0:2379:172.17.0.3:2379/tcp: address already in use
Run 'docker run --help' for more information
Steps to Reproduce the Problem
- Install the latest version of the Dapr CLI (currently running 1.17.1, but also reproduced against the most recent version of the 1.16 CLI) on Windows 11 (e.g.
winget install Dapr.CLI)
- Open terminal and type
dapr init
- Observe that it's unable to start up dapr_scheduler.
It installs the containers, but trying to start the scheduler within Docker Desktop yields a similar message:
(HTTP code 500) server error - failed to set up container networking: driver failed programming external connectivity on endpoint dapr_scheduler (c0d2832b04cf52e343a527f587d5573360198c08880cfe5b172e38f13aa5461c): failed to bind host port for 0.0.0.0:2379:172.17.0.5:2379/tcp: address already in use
Release Note
RELEASE NOTE: FIX Able to run dapr init without error on Windows again
Expected Behavior
I would like to open a terminal window, and using the installed Dapr CLI run
dapr initand see:Actual Behavior
_> dapr init
Steps to Reproduce the Problem
winget install Dapr.CLI)dapr initIt installs the containers, but trying to start the scheduler within Docker Desktop yields a similar message:
Release Note
RELEASE NOTE: FIX Able to run
dapr initwithout error on Windows again