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

Build succeeded.

• containerd-build-arm64 : SUCCESS in 3m 54s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 30s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 23m 55s (non-voting)

Is this a backport or did you cherry-pick the commits from main to release/1.5? If they can be cherry-picked we like to use the -x flag so the origin commit is listed in the commit entry.

If you didn't cherry-pick and had to backport we usually put that in the title; e.g. [release/1.5] backport: {original PR title}

I use cherry-pick. I will redo it using the -x flag.

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 20s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 20s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 23m 44s (non-voting)

Build succeeded.

• containerd-build-arm64 : SUCCESS in 3m 45s (non-voting)
• containerd-test-arm64 : SUCCESS in 4m 50s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 23m 49s (non-voting)