From 52e9e6259077d66c773cace454b9af1d5080f61a Mon Sep 17 00:00:00 2001 From: Whit Waldo Date: Wed, 26 Mar 2025 10:01:25 -0500 Subject: [PATCH] Added troubleshooting step to resolve port conflicts during `dapr init` on Windows Signed-off-by: Whit Waldo --- .../troubleshooting/common_issues.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/daprdocs/content/en/operations/troubleshooting/common_issues.md b/daprdocs/content/en/operations/troubleshooting/common_issues.md index 40281dd2fee..8d6294f6b4d 100644 --- a/daprdocs/content/en/operations/troubleshooting/common_issues.md +++ b/daprdocs/content/en/operations/troubleshooting/common_issues.md @@ -291,3 +291,21 @@ kubectl config get-users ``` You may learn more about webhooks [here](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/). + +## Ports not available during `dapr init` +You might encounter the following error on Windows after attempting to execute `dapr init`: + +> PS C:\Users\You> dapr init +Making the jump to hyperspace... +Container images will be pulled from Docker Hub +Installing runtime version 1.14.4 +Downloading binaries and setting up components... +docker: Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:52379 -> 0.0.0.0:0: listen tcp4 0.0.0.0:52379: bind: An attempt was made to access a socket in a way forbidden by its access permissions. + +To resolve this error, open a command prompt in an elevated terminal and run: + +```bash +nat stop winnat +dapr init +net start winnat +``` \ No newline at end of file