This problem is related to a bug in docker on macOS This is a issue that frequently occurs when running kind alongside Docker For Mac. Skewed too far from the kind node version. You may have problems interacting with your kind cluster if your client(s) are Then run kind export logs to export the logs from the container to a temporary directory on the host. If the cluster fails to create, try again with the -retain option (preserving the failed container), Failure to Create Cluster with Docker Desktop as Container Runtime.Couldn’t find an alternative telinit implementation to spawn.IPv6 Port Forwarding (docker doesn’t seem to implement this correctly).AppArmor (may break things, consider disabling).Chrome OS (needs KubeletInUserNamespace).Non-AMD64 Architectures (images not pre-built yet).Windows Containers (unsupported / infeasible).

Docker Permission Denied (ensure you have permission to use docker).

Pod Errors Due to “too many open files” (likely inotify limits which are not namespaced).

Failure to Create Cluster with Cgroups v2 (only supported for Kubernetes >= 1.19).

Failing to Properly Start Cluster (various causes).

Failure to Build Node Image (usually need to increase resources).

Docker Installed With Snap (snap filesystem restrictions problematic).

Older Docker Installations (untested, known to have bugs).

Kubectl Version Skew (Kubernetes limits supported version skew).

reach out and ask for help in #kind on the kubernetes slack.file an issue (if there isn’t one already).Having problems with kind? This guide covers some known problems and solutions / workarounds.

For mac download Process Explorer 17.05