Incorrect Dapr Redis StateStore Source Used about cli HOT 7 CLOSED

I think this may make sense.

@mukundansundar this seems more of a CLI issue, can you transfer the issue please?

from cli.

Dapr will connect to the Redis instance defined in the ~/.dapr/components/statestore.yaml file (which is created when you run dapr init). The default is localhost:6379.

In your case, it seems more like an issue with the Windows/WSL networking stack, since you had two instances of Redis (listening on the same port)?

from cli.

Dapr will connect to the Redis instance defined in the ~/.dapr/components/statestore.yaml file (which is created when you run dapr init). The default is localhost:6379.

Tracking. localhost:6379 is the default port that Redis listens when it is installed. If the intent is for Dapr to connect to the instance running in dapr_redis after running dapr init, perhaps it might be better to have it run on a different port and adjust the default configuration accordingly? This way, you can better project that Dapr is interfacing with the correct instance.

At the very least, it might be helpful to make a note of this in the documentation (maybe in the Initialize Dapr document, as well as this section) as this was pretty difficult for someone new to Dapr to pinpoint on first approach.

from cli.

This issue has been automatically marked as stale because it has not had activity in the last 60 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.

from cli.

This issue has been automatically closed because it has not had activity in the last 67 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.

from cli.

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.

from cli.

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.

from cli.