We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Show correct dapr-http-port and dapr-grpc-port env in docker-compose.yml.
Always show http: 3500 and grpc: 50001.
version: '3.4' name: "test-compose" services: dapr-placement: image: "daprio/dapr" command: [ "./placement", "-port", "50000" ] ports: - "50000:50000" networks: - dapr-network dapr-dashboard: image: "daprio/dashboard:latest" command: [ "--docker-compose=true", "--components-path=/components", "--config-path=/components/config.yaml", "--docker-compose-path=/home/nonroot/docker-compose.yml" ] volumes: # - "./dockercompose/dapr/components/:/home/nonroot/components" # - "./dockercompose/dapr/config/:/home/nonroot/configuration" - ./docker-compose.yml:/home/nonroot/docker-compose.yml - ./dapr:/components networks: - dapr-network ports: - "8080:8080" ############################ # Dapr sidecar for publisher ############################ publisher-dapr: image: "daprio/daprd:edge" command: [ "./daprd", "-app-id","opc-publisher-test1", "-components-path","/components", "-dapr-http-port","7001", "-dapr-grpc-port","7002", "-placement-host-address", "dapr-placement:50000", "-app-port","777" ] # network_mode: "host" networks: - dapr-network ports: - "7001:7001" - "7002:7002" - "3500:3500" - "50001:50001" volumes: - "./dapr:/components" depends_on: - dapr-dashboard - dapr-placement
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected Behavior
Show correct dapr-http-port and dapr-grpc-port env in docker-compose.yml.
Actual Behavior
Always show http: 3500 and grpc: 50001.
Steps to Reproduce the Problem
The text was updated successfully, but these errors were encountered: