fix: duplicate images coming with <none>:<none> tag

[aryasoni98]

What type of PR is this?

/kind bug

What this PR does / why we need it:
This PR resolves the issue of duplicate Docker images showing up with <none>:<none> tags when using containerd and nerdctl. The solution involves adding a task to remove these duplicate images after containerd setup.

Which issue(s) this PR fixes:
Fixes #11101

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Fixed issue of duplicate Docker images with <none>:<none> tags by removing dangling images post containerd setup.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: aryasoni98 / name: Arya Soni (ff95796, 7a32afd, d4aaa60, 81f8e81, 9314028)

[k8s-ci-robot]

Welcome @aryasoni98!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @aryasoni98. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aryasoni98
Once this PR has been reviewed and has the lgtm label, please assign liupeng0518 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[VannTen]

It's not clear at all this is an actual problem rather than some artifacts of the display by nerdctl (and others). Moreover, you should not add tasks directly to cluster.yml

[aryasoni98]

It's not clear at all this is an actual problem rather than some artifacts of the display by nerdctl (and others). Moreover, you should not add tasks directly to cluster.yml

Thank you for the feedback.

It's understood that the issue might stem from artifacts of the display by tools like nerdctl and others. The intention behind the changes was to ensure clarity and consistency across different environments, but I appreciate the clarification that tasks should not be added directly to cluster.yml. Instead, I will refactor the changes to ensure modularity and maintain the intended structure without directly modifying cluster.yml.

Your guidance is valuable for maintaining best practices in the project. Thank you for the direction.