First of all, thanks for making this useful project open source! 👏

I'm trying to run the example server inside a Docker container but didn't succeed. The example client was able to establish a connection, but got the error below:

2020/06/15 22:43:41 Connecting to 127.0.0.1:5501...
INFO: 2020/06/15 22:43:41 parsed scheme: ""
INFO: 2020/06/15 22:43:41 scheme "" not registered, fallback to default scheme
INFO: 2020/06/15 22:43:41 ccResolverWrapper: sending new addresses to cc: [{127.0.0.1:5501 0  <nil>}]
INFO: 2020/06/15 22:43:41 ClientConn switching balancer to "pick_first"
INFO: 2020/06/15 22:43:41 pickfirstBalancer: HandleSubConnStateChange: 0xc000099390, CONNECTING
INFO: 2020/06/15 22:43:41 pickfirstBalancer: HandleSubConnStateChange: 0xc000099390, READY
2020/06/15 22:43:41 Connected
INFO: 2020/06/15 22:43:41 pickfirstBalancer: HandleSubConnStateChange: 0xc000099390, TRANSIENT_FAILURE
2020/06/15 22:43:41 client.Start: rpc error: code = Unavailable desc = transport is closing

Reading the example's docs I noticed a comment, The client failed ("transport is closing") because the agent is using TLS but the client is not., but I didn't set any TLS config, so I don't think it makes sense in this case.

If you have any suggestions, please advise!

Thanks!

Is this project still active? Is there any plans to update it with usage examples and update the golang version and other dependencies?

Hi. I like your project! I would like to try it without building. Is it possible?

Hi there,
We have been discussing the possibility of using rce-agent to add a container-to-container communication feature to GitLab Runner's Custom Executor driver for AWS Fargate. The related issue is Support a fargate-agent sidecar container to prevent the need for custom CI images.

We made good progress in the proof-of-concept, but now we are blocked by the rce-agent's command whitelisting feature. This is a blocker because the driver is used to run CI/CD pipelines and we cannot anticipate the commands users will set up in their jobs, and hence we cannot whitelist them.

So the primary goal of this issue is to ask rce-agent's team if it makes sense to turn the command whitelisting feature optional. Based on the answer we can decide whether it's worth keeping the conversation going. 🙂

Thanks in advance!

while building client binary pb package is not finding. Hence it is failed.