Docs: Add docs for nerdctl support

[yankay]

After the #3429, the nerdctl is supported.

So add it to the docs.

[neolit123]

/lgtm

[nunix]

hi everyone,

first of all, thanks a lot for this feature and the documentation of it 😄

I did a quick test on the Finch WSL2 distro, and here's the output:

In the docs, I don't think there's the mention of the environment variable KIND_EXPERIMENTAL_PROVIDER, however as you can see, depending on when the docs will come out, we might need to mention it.

If you think/know this won't be needed as there's possibly an internal check, then please disregard my comment.

Once again, thanks a lot for the great work.

[AkihiroSuda]

https://kind.sigs.k8s.io/docs/user/rootless/ should be updated too

[AkihiroSuda]

I also guess that KIND_EXPERIMENTAL_PROVIDER should be explained somewhere

[yankay]

https://kind.sigs.k8s.io/docs/user/rootless/ should be updated too

Thanks, it has been updated.

[AkihiroSuda]

Suggested change

	To create a kind cluster with Nerdctl Podman, just run:
	To create a kind cluster with nerdctl, just run:

[AkihiroSuda]

nit: maybe s/Nerdctl/nerdctl/g

[yankay]

Thanks, it has been updated.
And add some docs for KIND_EXPERIMENTAL_PROVIDER : https://github.com/kubernetes-sigs/kind/pull/3532/files#diff-40a589d72dc1d461ea36579cd051d1adf7ca6ea6bdc2c7dcda6a714130910486

[yankay]

hi everyone,

first of all, thanks a lot for this feature and the documentation of it 😄

I did a quick test on the Finch WSL2 distro, and here's the output:

In the docs, I don't think there's the mention of the environment variable KIND_EXPERIMENTAL_PROVIDER, however as you can see, depending on when the docs will come out, we might need to mention it.

If you think/know this won't be needed as there's possibly an internal check, then please disregard my comment.

Once again, thanks a lot for the great work.

Thanks @nunix

Because I do have a finch WSL environment, I can only try to reproduce the issue in Ubuntu Linux.

root@kay201:~/oss/kind# docker version
-bash: /usr/local/bin/docker: No such file or directory
root@kay201:~/oss/kind# nerdctl version
Client:
 Version:       v1.7.2-102-gc18036e2.m
root@kay201:~/oss/kind# ./bin/kind --version
kind version 0.23.0-alpha.10+7c3e01fc1c25d8
root@kay201:~/oss/kind# ./bin/kind create cluster
Creating cluster "kind" ...
⠈⡱ Ensuring node image (kindest/node:v1.29.2) 🖼

It can work correctly without KIND_EXPERIMENTAL_PROVIDER , because the kind can auto-detect provider by https://github.com/kubernetes-sigs/kind/blob/main/pkg/cluster/provider.go#L114 .

Would you please help to provide the output with commands

nerdctl -v 
finch -v

to help me invesgate the issue :-)

[nunix]

nerdctl -v

@yankay certainly, here's the output (screenshot just for proof):
nerdctl version 1.7.3 (from Rancher Desktop install)
finch version v1.1.2

On the KinD side, I generated the binary from WSL2 Finch distro with the command make install INSTALL_DIR=/usr/local/bin (inside the git KinD directory).
The KinD version is:
kind v0.23.0-alpha.10+7c3e01fc1c25d8 go1.20.13 linux/amd64

Finally, I also built kind.exe, with the command GOOS=windows go build from WSL2.
The version is:
kind v0.23.0-alpha go1.21.7 windows/amd64

Same as before with nerdctl, I had to set KIND_EXPERIMENTAL_PROVIDER, to finch this time, to be able to create the cluster (see screenshot below for the whole process).

hope this helps and please let me know if I need to run specific commands for building it on WSL2/Windows.

[aojea]

@nunix is your concern addressed by this comment?

[nunix]

@aojea yes all good on my side for the comment.

I will try again the auto-detect when the 0.23 is out maybe, as what I was trying to test was actually the auto-detect. But it's maybe on my side and with the comment, it provides the needed help.

[aojea]

waiting for resolving the last comment

[aojea]

/lgtm
/approve
Thanks

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AkihiroSuda, aojea, yankay

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [aojea]

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