Hi @jjmaestro. 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.

Good bot :)

hmm... so, some checks have failed! I'm surprised since the change is a doc change so... :-? are these caused by flaky tests or something similar? Looking at the failed checks it does look like it could be that, I think?

🎉 Thanks! :)