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

can't run hello-world in dev container #499

Closed
spottedmahn opened this issue Dec 6, 2021 · 4 comments
Closed

can't run hello-world in dev container #499

spottedmahn opened this issue Dec 6, 2021 · 4 comments

Comments

@spottedmahn
Copy link
Contributor

Expected Behavior

I can debug the node hello-world app in a dev container

Actual Behavior

Error: A compatible version of Dapr has not been initialized. You may need to install a more recent version.

Steps to Reproduce the Problem

  1. clone repo in wsl
  2. cd quickstarts
  3. code-insiders .
  4. update dev container image to 1.6.9, reference: Rvm default gid conflicts with user gid syncing
  5. say yes when prompting if you want to open a dev container
  6. open the hello-world folder
  7. run debugger on node app

image

image

image


image

image

@wcs1only
Copy link
Contributor

wcs1only commented Dec 6, 2021

This is a good case for resurrecting #448

@paulyuk
Copy link
Contributor

paulyuk commented Jan 16, 2022

Hey @spottedmahn - sorry about this. we need to dig into why. I can see that daprd is not by default where it's expected. this looks like an incomplete install from dockerfile.

To workaround for now you can do this from the VS-Code Terminal:
dapr uninstall --all
dapr init

You should no longer see the dapr_placement container already exists because the uninstall step cleaned that up. then you should be able to do this with success:

dapr run --app-id nodeapp --app-port 3000 --dapr-http-port 3500 node app.js

@paulyuk
Copy link
Contributor

paulyuk commented Jan 23, 2022

@spottedmahn any chance you want to test and approve the PR I have above?

@paulyuk
Copy link
Contributor

paulyuk commented Feb 25, 2022

I believe this is fixed, but please reopen if not

@paulyuk paulyuk closed this as completed Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants