Then I realized that Dapr sidecar information for each service is present in the docker-compose.override.yml, causing the dashboard to miss detecting them.
I am unsure whether this behavior is a bug or if it's intended to have only -docker-compose-path arg, so we should always put the sidecars info in the docker-compose.yml file?
I was trying to use Dapr dashboard inside the docker compose of EShopOnDapr https://github.com/dotnet-architecture/eShopOnDapr, But I got an empty list of the applications as below
Then I realized that Dapr sidecar information for each service is present in the docker-compose.override.yml, causing the dashboard to miss detecting them.
I am unsure whether this behavior is a bug or if it's intended to have only -docker-compose-path arg, so we should always put the sidecars info in the docker-compose.yml file?