Closed abalmos closed 2 years ago
containerd doesn't expose all APIs via TTRPC, just events endpoint, which is used by shims. You'd need to use GRPC for everything else.
@mxpv Well, that explains it :smile: The error was pretty telling after all.
In the meantime I had been working on a tonic
based solution and have had success. I will continue down that path then.
Thanks for the help!
You might be interested in this: https://github.com/containerd/project/issues/82
@mxpv I would be. I started working on a containerd rust library today. It seems the repo is not available?
It'll be open sourced once the voting is done (if approved (: )
I see. Is the library complete? I'll keep working on my solution in the meantime.
@abalmos you can now give it a try, repo is here: https://github.com/containerd/rust-extensions
Description of problem
All of my attempts to use ttrpc-rust to connect to the containerd deamon is failing. I'm sure I am doing something wrong, but I can't seem to send a request such that the service is found. Would you have any immediate thoughts on that?
I've used the protobuf files from here: https://github.com/containerd/containerd/tree/main/api
Expected result
A print out of
ListTaskResponse
Actual result
Side question: containerd's Content protobuf's use a few stream responses. Those result in compile time errors when built with ttrpc-rust. Are streaming responses not supported by ttrpc-rust?
Thank you for the help and the all the work to bring this functionality to rust!