I would expect the dashboard to display all the Dapr Applications in the Overview.
Actual Behavior
Given I run the dashboard using the docker compose = true
When any of my other service (simple dotnet app) uses the env_file: property
Then the dashboard would show an empty Dapr Applications in the Overview page.
Steps to Reproduce the Problem
Create a simple docker compose file with one service and
Then if we open the logs for the dashboard, we can observe this line, even though the image for the dashboard should not load the .env files:
024/07/08 09:43:57 Failed to load /infra/dapr/envs/var-features.env: open /infra/dapr/envs/var-features.env: no such file or directory
Release Note
FIX env_file to be use for another service does not break initialization of the dashboard.
Expected Behavior
I would expect the dashboard to display all the Dapr Applications in the Overview.
Actual Behavior
Given I run the dashboard using the docker compose = true When any of my other service (simple dotnet app) uses the env_file: property Then the dashboard would show an empty Dapr Applications in the Overview page.
Steps to Reproduce the Problem
Create a simple docker compose file with one service and
, one dapr sidecar based on image: "daprio/daprd:latest" with
, and one dashboard with image: "daprio/dashboard:latest" and
Then if we open the logs for the dashboard, we can observe this line, even though the image for the dashboard should not load the .env files:
024/07/08 09:43:57 Failed to load /infra/dapr/envs/var-features.env: open /infra/dapr/envs/var-features.env: no such file or directory
Release Note
FIX env_file to be use for another service does not break initialization of the dashboard.