Hi @kit-ty-kate. 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.

How about using sysctl? golang/go#47006 (comment)
What is the negative side-effects of detecting ARMv7 as unknown? If it doesn't have any, I'm fine having a stopgap solution for now.

I think using a sysctl is probably fine, but it sounds like @kit-ty-kate isn't in a position to test whether that works across other variants. The change in this PR seems like a strict improvement to me over the prior behavior of unconditionally returning an error. If we're concerned about the "unknown" value, we could (as a stopgap) make that branch continue to return an error.

The change looks good, but you need to have the DCO (signed-off line).

Can you try git commit --amend -s? Please make sure your email address and name are valid.

The two failing tests look like flakes - could someone re-run them?

@kit-ty-kate Can you rebase this branch to have #7539? This would fix rockylinux/8 build.

@kzys I just did that but that didn't help

At least you don't have the failure on rockylinux/8 anymore. Let me re-run other failed ones.

/ok-to-test

It wouldn't impact Kubernetes though.