-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
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
Question about your content store plugin #10
Comments
You should use the gRPC plugin interface, so the compatibility is happening at a protobuf API level not a go plugin level. https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#proxy-plugins |
I had created a content store based on the snapshotter plugin. However, it’s unclear how to connect my store implementation with the RPC service. For snapshotter we:
With that in place my snapshotter works fine. However, for the content store I am a little lost. For content there's a |
You need to disable the built in one. See the containerd config here as a reference: https://github.com/hinshun/ipcs/blob/master/cmd/containerd/config.toml#L4 |
It's done. When I try to do a pull I get an "unimplemented" error. I was wondering if the IPCS implementation chose to use the |
I'm not sure I understand. Why not just use these: cssvc := contentserver.New(cs)
cssvc.Register(rpc) IPCS should be using the proxy mechanism, its been a few years so it's unclear why it chose the |
With my gRPC implementation I had:
Because using:
Resulted in:
As
The registration provides no feedback so it's not clear if things are set. I see a connection come in:
But no traffic flows and when I do a pull:
Which seems to tell me I really haven't registered properly. |
Got it - i had incorrectly named the type Thanks for the suggestions, they helped enormously. |
I think the registration is still (a/the) problem. The value returned by
The significant part is that the type is
So why does it tell me:
|
I have created a discussion on |
When I build a plugin
containerd
will complain with "plugin was built with a different version ...". I am building with the same level ofgolang
ascontainerd
and mygo.mod
has the same level ofcontainerd
that I am running but I cannot get rid of this. How did you avoid it?The text was updated successfully, but these errors were encountered: