Dapr客户端Docker撰写问题

Question

我在本地Docker实例中尝试将3个服务与Dapr集成。每个服务都在Linux容器中运行。

version: '3.4'
networks:
  NextWare:
    external: true
services:
  nextware.daprtest.service1.api:
    environment:
      - ASPNETCORE_ENVIRONMENT=Development
      - DAPR_GRPC_PORT=40001
    ports:
      - "40001:40001" # Dapr instances communicate over gRPC so we need to expose the gRPC port
      - "4001:80"
    depends_on:
      - redis
      - placement
    networks:
      - NextWare
    volumes:
      - ${APPDATA}/Microsoft/UserSecrets:/root/.microsoft/usersecrets:ro

  nextware.daprtest.service1.api-dapr:
    image: "daprio/daprd:edge"
    command: [
      "./daprd",
     "-app-id", "nextware.daprtest.service1.api",
     "-app-port", "3001",
     "-dapr-grpc-port", "40001",
     "-metrics-port", "9091",
     "-placement-host-address", "placement:50006", # Dapr's placement service can be reach via the docker DNS entry
     "-components-path", "/components"]

    volumes:
        - "./components/nextware.daprtest.service1.api:/components" # Mount our components folder for the runtime to use
    depends_on:
      - nextware.daprtest.service1.api
    network_mode: "service:nextware.daprtest.service1.api" # Attach the nodeapp-dapr service to the nodeapp network namespace

  nextware.daprtest.service2.api:
    environment:
      - ASPNETCORE_ENVIRONMENT=Development
      - DAPR_GRPC_PORT=40003
    ports:
      - "40003:40003" # Dapr instances communicate over gRPC so we need to expose the gRPC port
      - "4003:80"
    depends_on:
      - redis
      - placement
    networks:
      - NextWare
    volumes:
      - ${APPDATA}/Microsoft/UserSecrets:/root/.microsoft/usersecrets:ro

  nextware.daprtest.service2.api-dapr:
    image: "daprio/daprd:edge"
    command: [
      "./daprd",
     "-app-id", "nextware.daprtest.service2.api",
     "-app-port", "3003",
     "-dapr-grpc-port", "40003",
     "-metrics-port", "9093",
     "-placement-host-address", "placement:50006" # Dapr's placement service can be reach via the docker DNS entry
     ]
    volumes:
        - "./components/nextware.daprtest.service2.api:/components" # Mount our components folder for the runtime to use
    depends_on:
      - nextware.daprtest.service2.api
    network_mode: "service:nextware.daprtest.service2.api" # Attach the nodeapp-dapr service to the nodeapp network namespace


  nextware.daprtest.service3.api:
    environment:
      - ASPNETCORE_ENVIRONMENT=Development
      - DAPR_GRPC_PORT=40005
    ports:
      - "40005:40005" # Dapr instances communicate over gRPC so we need to expose the gRPC port
      - "4005:80"
    depends_on:
      - redis
      - placement
     
    networks:
      - NextWare
    volumes:
      - ${APPDATA}/Microsoft/UserSecrets:/root/.microsoft/usersecrets:ro


  nextware.daprtest.service3.api-dapr:
    image: "daprio/daprd:edge"
    command: [
      "./daprd",
     "-app-id", "nextware.daprtest.service3.api",
     "-app-port", "3005",
     "-dapr-grpc-port", "40005",
     "-metrics-port", "9095",
     "-placement-host-address", "placement:50006" # Dapr's placement service can be reach via the docker DNS entry
     ]
    volumes:
        - "./components/nextware.daprtest.service3.api:/components" # Mount our components folder for the runtime to use
    depends_on:
      - nextware.daprtest.service3.api
    network_mode: "service:nextware.daprtest.service3.api" # Attach the nodeapp-dapr service to the nodeapp network namespace

运行Docker PS时，我看到以下容器..

​

​

在服务启动并运行之后，我尝试从Service3到Service1调用以下代码...

 var request = _mapper.Map<UpdateRequest>(integrationCommand);
 await _daprClient.InvokeMethodAsync("nextware.daprtest.service1.api", "Update", request, cancellationToken);

我得到了以下异常...

​

​

RequestUri是否正确...

"http://127.0.0.1:3500/v1.0/invoke/nextware.daprtest.service1.api/method/Update“

鉴于这是调用sidecar的DaprClient，我假设上面的RequestUri是正确的。

我遗漏了什么？

Answer 1

错误的原因是由于ID和方法名的格式不正确。

我从Docker compose转到了Tye，也遇到了同样的问题。

然后，我根据这个屏幕截图更改了调用。

​

​

虽然这仍然没有调用到Update方法，但它不再返回500异常。

相反，我得到了下面的异常，我很难解决这个问题……

根据验证过程，远程证书无效: RemoteCertificateNameMismatch，RemoteCertificateChainErrors

​

​

这是由于下面的启动配置设置，我把它注释掉了，在那之后一切都工作得很好…

​

​

Dapr Rocks！