Hi @log1cb0mb. 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 13s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 12s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 12m 28s (non-voting)

Signed-off-by: log1cb0mb [email protected]

Please sign the commit using real name rather than username (https://github.com/containerd/project/blob/main/CONTRIBUTING.md#sign-your-work)

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 16s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 38s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 12m 34s (non-voting)

Looks like you may have to run go mod tidy from within the integration/client directory as well (which also has a go.mod);

Files /home/runner/work/containerd/containerd/src/github.com/containerd/containerd/integration/client/go.mod and /tmp/tmp.PYcoKntieN/containerd/integration/client/go.mod differ
Files /home/runner/work/containerd/containerd/src/github.com/containerd/containerd/integration/client/go.sum and /tmp/tmp.PYcoKntieN/containerd/integration/client/go.sum differ

/ok-to-test

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 32s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 25s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 23m 40s (non-voting)