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

Unable to start sidecar when using secrets components with dapr run -f #1411

Open
bondz opened this issue Jun 19, 2024 · 8 comments
Open

Unable to start sidecar when using secrets components with dapr run -f #1411

bondz opened this issue Jun 19, 2024 · 8 comments
Labels
kind/bug Something isn't working

Comments

@bondz
Copy link

bondz commented Jun 19, 2024

Expected Behavior

When running the a daprized app using the dapr cli, it should be able to read secrets defined in a configuration

Actual Behavior

The dapr sidecar is never started.

Steps to Reproduce the Problem

See a small repro here - https://github.com/bondz/dapr-secrets

Clone the repo.

cd my-service
npm install

There's a single secret defined in the .dapr/secrets.json file that the app (my-service) reads.

When running the app directly using dapr multi-app run in the root directory, the sidecar is never started.

dapr run -f .

It hangs for a while, eventually errors and exits.

alt text

However, if you use vscode and run the app using the launch configuration, passing the config flags directly, it works fine.

alt text

@bondz bondz added the kind/bug Something isn't working label Jun 19, 2024
@bondz
Copy link
Author

bondz commented Jun 20, 2024

When using dapr run -f ., daprd is looking for the file in the my-service directory rather than relative to where dapr run was invoked.

Moving the secret file to the same directory as the service is a workaround.

@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 Jul 20, 2024
@bondz
Copy link
Author

bondz commented Jul 20, 2024

Bot comment

@dapr-bot dapr-bot removed the stale label Jul 20, 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 Aug 19, 2024
@bondz
Copy link
Author

bondz commented Aug 19, 2024

Bot comment

@dapr-bot dapr-bot removed the stale label Aug 19, 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 stale and removed stale labels Sep 18, 2024
@bondz
Copy link
Author

bondz commented Sep 18, 2024

Bot comment

@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 stale and removed stale labels Oct 18, 2024
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
Projects
None yet
Development

No branches or pull requests

2 participants