Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Ports are not available" for dapr_scheduler in Windows using Docker #1464

Closed
boclifton-MSFT opened this issue Nov 13, 2024 · 2 comments
Closed
Labels
kind/bug Something isn't working stale

Comments

@boclifton-MSFT
Copy link

boclifton-MSFT commented Nov 13, 2024

Expected Behavior

Scheduler container starts as expected.

Actual Behavior

dapr init gives a Docker error:

PS C:\Users\boclifton> 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.

Docker Desktop reports this error: (HTTP code 500) server error - 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.

Steps to Reproduce the Problem

Started from a fresh installation and followed the instructions in Initialize Dapr in your local environment.

Release Note

RELEASE NOTE:
FIX: Docker port issue resolved with default dapr_scheduler port

@boclifton-MSFT boclifton-MSFT added the kind/bug Something isn't working label Nov 13, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Dec 13, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

2 participants