Closed justinyjsong closed 2 years ago
I think this is a docker networking "issue". You need to be able to reach a service running on your "localhost" from within a process that runs inside a container.
actually just a configuration issue, resolving this ticket. thanks.
Title: gRPC-JSON encoding issue: upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111
Description:
I used docker-compose which takes Dockerfile to deploy the service.
docker-compose.yaml
Dockerfile
envoy-local.yaml
and this is how I compile my protobuf which also contains googleapis and generate the proto_descriptor for json transcoding to be used.
running the gRPC server is as simple as
gRPCurl command worked
Here is my proto file that was compiled.
Now executing the below POST curl
Gives
I am not sure why envoy proxy is not able to catch the server. gRPC is running locally and envoy is running from docker container.
For further investigation, I have also provided my admin logs.
From the admin, output of
curl localhost:9901/clusters
Output of
curl localhost:9901/listeners
Output of
curl localhost:9901/stats
Would appreciate how to resolve this issue.