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

Thanks, but please sign the commit for DCO
https://github.com/apps/dco

(run git commit -a -s --amend, and make sure that the Signed-off-by: NAME <EMAIL> line with your real name is included in the commit message)

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 22s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 37s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 23m 56s (non-voting)

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 34s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 43s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 23m 41s (non-voting)