Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Build succeeded.

• containerd-build-arm64 : SUCCESS in 5m 51s (non-voting)

Shouldn't we use multi-arch image?

Cc @ktock

Yep, messed up archs somewhere. Repushed.

uploaded it by manually?

Yes, we don't have any automation for this.

Yes, we don't have any automation for this.

I was trying to upload the image by action. But I received the error like denied: installation not allowed to Create organization package. Still looking into it.

=====

check the information by manifest-tool. LGTM

manifest-tool inspect ghcr.io/containerd/busybox:1.32
Name:   ghcr.io/containerd/busybox:1.32 (Type: application/vnd.docker.distribution.manifest.list.v2+json)
Digest: sha256:ae39a6f5c07297d7ab64dbd4f82c77c874cc6a94cea29fdec309d0992574b4f7

manifest-tool inspect docker.io/library/busybox:1.32
Name:   docker.io/library/busybox:1.32 (Type: application/vnd.docker.distribution.manifest.list.v2+json)
Digest: sha256:ae39a6f5c07297d7ab64dbd4f82c77c874cc6a94cea29fdec309d0992574b4f7

Not to derail this incremental change, but I noticed what @claudiubelu is doing in #5163 and almost wonder if we could break out that commit as a separate PR as it streamlines a lot of the registry definitions/image names used within the various tests.

I was thinking we might even build on that underlying support to harden our tests with an array of locations for each image (e.g. mirroring) that would be fallbacks when pull fails during the test runs on the primary image name/registry location.

Not to derail this incremental change, but I noticed what @claudiubelu is doing in #5163 and almost wonder if we could break out that commit as a separate PR as it streamlines a lot of the registry definitions/image names used within the various tests.

I was thinking we might even build on that underlying support to harden our tests with an array of locations for each image (e.g. mirroring) that would be fallbacks when pull fails during the test runs on the primary image name/registry location.

Sure, I can separate that. I was mirroring the way Kubernetes E2E tests handles images.

Not to derail this incremental change, but I noticed what @claudiubelu is doing in #5163 and almost wonder if we could break out that commit as a separate PR as it streamlines a lot of the registry definitions/image names used within the various tests.

I was thinking we might even build on that underlying support to harden our tests with an array of locations for each image (e.g. mirroring) that would be fallbacks when pull fails during the test runs on the primary image name/registry location.

Sent a PR here: #5403

It's now easy to point to different source repos for test images now that #5403 is merged; of course I haven't seen a registry rate limit in awhile now either :)

yep, i'll go ahead and close this one.