This repository has been archived by the owner on Apr 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
containerd support #9
Comments
Any updates on this request? |
Thank you for the report, @obiTrinobiIntel and @davecremins . As far as I know of, multus-service should work with containerd because containerd supports cri. You may need to change deployment yaml to adopt the cri socket path, but it does not require any go code change. Could you please try that and let me know the feedback for that? Thanks! |
Thanks Tomo, we will modify the yaml spec and deploy. I will post updates
here once we run the test.
…On Tue, Aug 2, 2022 at 7:49 PM Tomofumi Hayashi ***@***.***> wrote:
Thank you for the report, @obiTrinobiIntel
<https://github.com/obiTrinobiIntel> and @davecremins
<https://github.com/davecremins> .
As far as I know of, multus-service should work with containerd because
containerd supports cri. You may need to change deployment yaml to adopt
the cri socket path, but it does not require any go code change.
Could you please try that and let me know the feedback for that? Thanks!
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJTM3X3TOIZR3SOJK3UBYTVXFUTFANCNFSM54SYSXIQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@davecremins It is 3month+ since you replied. Did you check that? If you don't mind it, I will close this issue. |
@davecremins followup. Does it works? If you don't test it yet, I will test it and close this if it works. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Multus service currently can be configured with docker and crio, is it possible to support containerd runtime ?
The text was updated successfully, but these errors were encountered: