dapr/cli

No Dapr instances found when there is at least one instance running

JFCote opened this issue · 4 comments

JFCote commented

In what area(s)?

Not sure

Ask your question here

I'm not sure if it's a bug or not and my colleagues do not have this problem on their setup...

When I do the following:

dapr run --app-id myapp --dapr-http-port 3601 --dapr-grpc-port 6001 --app-port 7154 --app-ssl

And then in another terminal, I do this:

dapr list

I receive this response:

No Dapr instances found.

I have tried this so far:

  • Reboot my computer multiple times
  • Run dapr uninstall --all and dapr init at least 3 times

I'm out of ideas as to what to do next since I absolutely need to "detect" instances to publish to them using dapr command line to test my application.
Is there anything else I can do to start "fresh" with Dapr?

Notice that Dapr itself seems to work well since my app is running and talking with the sidecar without problems.

JFCote commented

UPDATE: I have uninstalled "dapr CLI" using Windows Uninstall and after doing dapr init it started to work again.
I don't know what is the difference between doing dapr uninstall --all and doing the uninstall from the command line, but that did the trick.

UPDATE: I have uninstalled "dapr CLI" using Windows Uninstall

Could you share more on how did you uninstall this?

dapr uninstall --all uninstalls the dapr runtime (binaries and containers) and dev resources (like redis, zipkin) from your %USERPROFILE%.dapr path, but the "Dapr CLI" itself does not get uninstalled.

If you were still able to run dapr init after uninstalling "Dapr CLI", that smells like multiple "Dapr CLI" installations which could cause what you were seeing.

JFCote commented

@shubham1172 It's totally possible. The way I was able to completely remove dapr was with Windows Uninstall, like any other application.
After that, I did dapr init and it worked.

To be honest, I don't remember having install dapr multiple time but since it's a dev machine, everything is possible ;)

Thanks @JFCote, we will close this issue then, please feel free to open another one if you face further issues.