Open krachynski opened 6 months ago
You need to specify KIND_EXPERIMENTAL_PROVIDER=podman if you have both podman and docker on your machine
Interesting, I don't recall the UI mentioning that at all. Is it at least documented for command line use?
Interesting, I don't recall the UI mentioning that at all. Is it at least documented for command line use?
See https://kind.sigs.k8s.io/docs/user/quick-start/#creating-a-cluster
Ah, I never went to the kind documentation because I started from the Podman Desktop perspective. This is an extension provided by PD and thus would have been documented along with it.
This issue has been automatically marked as stale because it has not had activity in the last 6 months. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!
Bug description
I had a need to completely recreate my podman-machine-default instance and once I got everything updated, kind was unable to create a cluster for me. It went through the motions of ensuring the node image, preparing the node, writing the configuration, and starting the control-plane. This final step eventually fails.
After preparing to copy the log, I finally noticed that kind is calling docker to verify that the node came up.
I have docker installed and configured with multiple contexts to manage the several remote nodes in our network. kind was installing it's node and then checking the remote node for health... none of the necessary software existed on that node.
Operating system
Windows 11 Pro 23H3 (10.0.22631.3155)
Installation Method
Winget (Windows)
Version
1.7.0
Steps to reproduce
kind init
Relevant log output
Additional context
I didn't notice the docker call until I went to copy the log. At which point I understood why the kind container never showed up on my local podman machine.