Hi @AdamKorcz. 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 4m 38s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 43s (non-voting)
• containerd-integration-test-arm64 : FAILURE in 28m 38s (non-voting)

/ok-to-test

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 22s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 48s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 25m 21s (non-voting)

@estesp can you take a look?