-
Notifications
You must be signed in to change notification settings - Fork 18
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
error establishing client to placement service #82
Comments
@Annonator Are you on Windows, by chance? Looking into this, I think I may have found an issue where the default placement address is supposed to be different on Windows vs. other platforms but, for whatever reason, the issue wasn't apparent in prior versions. In any case, if you're on Windows, try setting the |
Yes I'm running on windows :) Added the property and i can confirm that it works now. |
This gets really tricky when you are running windows, but using dev containers on WSL2, with native docker :) I can confirm this also works in my configuration:
|
@ElanHasson Glad the workaround works. Yes, WSL2 might make things interesting. How are you running the Dapr extension, "locally" (i.e. in Windows) or "remotely" from WSL2? |
Remotely, from Dev containers via in WSL2 |
Hi all,
i recently played around with Dapr and the vscode plugin, i installed the most recent runtime / CLI https:/dapr/dapr/releases/tag/v0.5.0
https:/dapr/dapr/releases/tag/v0.5.1
My sample application runs without any major problems if I manually user daprd, dapr and attach the debugger. However, after installing the extension I did "scaffold dapr tasks" and i do run in the following error when executing the task:
As a note here, if I start daprd, dapr manually i only use the following:
and I can attach my debugger to it without any problems. The main difference here is that i do not define a placement service address which is done automatically when i use the extension.
This problem might be very well related to my setup, what I'm struggling with is the amount of control i have to fix this through the plugin as I could not find a way to not set a placement-address through configuration (which might be just missing knowledge)
My launch.json:
and my tasks.json
The text was updated successfully, but these errors were encountered: