Description

It's caused by new change on image.

REF: kubernetes-sigs/cri-tools#1950

Steps to reproduce the issue

Just file pull request to trigger CI pipleine

Describe the results you received and expected

Should not fail

What version of containerd are you using?

main

Any other relevant information

Before upstream supports windows-2022, we should ignore these 5 test cases.

Summarizing 5 Failures:
[FAIL] [k8s.io] Image Manager [It] public image with tag should be pulled and removed [Conformance]
sigs.k8s.io/cri-tools/pkg/framework/util.go:390
[FAIL] [k8s.io] Image Manager [It] public image without tag should be pulled and removed [Conformance]
sigs.k8s.io/cri-tools/pkg/framework/util.go:390
[FAIL] [k8s.io] Image Manager [It] image status should support all kinds of references [Conformance]
sigs.k8s.io/cri-tools/pkg/framework/util.go:390
[FAIL] [k8s.io] Image Manager [It] listImage should get exactly 3 image in the result list [Conformance]
sigs.k8s.io/cri-tools/pkg/framework/util.go:390
[FAIL] [k8s.io] Image Manager [It] listImage should get exactly 3 repoTags in the result image [Conformance]
sigs.k8s.io/cri-tools/pkg/framework/util.go:390

Show configuration if it is related to CRI plugin.

No response