Use cgr.dev/chainguard/wolfi-base base image

[AnishShah]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

Chainguard Images is a collection of container images designed for minimalism and security. These images are built from the latest source every night and ensure that the vulnerabilities are addressed ASAP.

Switching to cgr.dev/chainguard/wolfi-base from alpine will help fix vulnerabilities from the base image.

Which issue(s) this PR fixes:

Fixes #402

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Welcome @AnishShah!

It looks like this is your first PR to kubernetes-csi/csi-driver-host-path 🎉. 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-csi/csi-driver-host-path 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AnishShah
Once this PR has been reviewed and has the lgtm label, please assign xing-yang 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

[k8s-ci-robot]

Hi @AnishShah. Thanks for your PR.

I'm waiting for a kubernetes-csi 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/test-infra repository.

[msau42]

/ok-to-test

[msau42]

The k8s project has generally recommended distroless or debian base images. Can we use one of those instead?

[jsafrane]

The driver uses tar for snapshots, cp for cloning and who knows what else for block volumes (fallocate, mkfs, ...)

[k8s-ci-robot]

@AnishShah: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-csi-csi-driver-host-distributed-on-kubernetes-1-25	6cc5df4	link	false	/test pull-kubernetes-csi-csi-driver-host-distributed-on-kubernetes-1-25
pull-kubernetes-csi-csi-driver-host-path-1-24-on-kubernetes-1-24	6cc5df4	link	true	/test pull-kubernetes-csi-csi-driver-host-path-1-24-on-kubernetes-1-24
pull-kubernetes-csi-csi-driver-host-path-1-24-test-on-kubernetes-1-24	6cc5df4	link	false	/test pull-kubernetes-csi-csi-driver-host-path-1-24-test-on-kubernetes-1-24
pull-kubernetes-csi-csi-driver-host-path-1-26-on-kubernetes-1-26	6cc5df4	link	false	/test pull-kubernetes-csi-csi-driver-host-path-1-26-on-kubernetes-1-26
pull-kubernetes-csi-csi-driver-host-path-1-26-test-on-kubernetes-1-26	6cc5df4	link	false	/test pull-kubernetes-csi-csi-driver-host-path-1-26-test-on-kubernetes-1-26
pull-kubernetes-csi-csi-driver-host-path-1-25-on-kubernetes-1-25	6cc5df4	link	true	/test pull-kubernetes-csi-csi-driver-host-path-1-25-on-kubernetes-1-25
pull-kubernetes-csi-csi-driver-host-path-1-25-test-on-kubernetes-1-25	6cc5df4	link	false	/test pull-kubernetes-csi-csi-driver-host-path-1-25-test-on-kubernetes-1-25

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

[pohly]

These images are built from the latest source every night and ensure that the vulnerabilities are addressed ASAP.

That doesn't help because csi-driver-host-path then still needs to be updated. I still don't see why that is needed "ASAP" - it's a demo driver for testing.