Hi @voltbit. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Hey Mike, thanks for the comment, my commit is already signed with my personal email. You mean I should also add the 'Signed-off' message to my commit message?

L.E. I've just read the CONTRIBUTING.md, applogies for not checking it first. I've added the text to my commit message.

Hey Mike, thanks for the comment, my commit is already signed with my personal email. You mean I should also add the 'Signed-off' message to my commit message?

L.E. I've just read the CONTRIBUTING.md, applogies for not checking it first. I've added the text to my commit message.

sry about the DCO hassle :-) The reason I mentioned using -s for signing is it's hard to get that cut and paste just right.

Here's an example:

update for cni config

Signed-off-by: Mike Brown <[email protected]>

# Please enter the commit message for your changes. Lines starting

note description is one line and fairly short; note blank line before and after signature... I didn't pull your commit header but it's usually one of those details...

Thanks!