kind: BUG: create cluster with ipv6 fails
What happened: config.yaml:
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
networking:
ipFamily: ipv6
*exactly as in https://kind.sigs.k8s.io/docs/user/configuration/
$ kind create cluster --config=config.yaml
Creating cluster “kind” …
✓ Ensuring node image (kindest/node:v1.17.0) 🖼
✓ Preparing nodes 📦
✓ Writing configuration 📜
✗ Starting control-plane 🕹️
ERROR: failed to create cluster: failed to init node with kubeadm: command “docker exec --privileged kind-control-plane kubeadm init --ignore-preflight-errors=all --config=/kind/kubeadm.conf --skip-token-print --v=6” failed with error: exit status 1
Environment: $ kind version kind v0.7.0 go1.13.5 linux/amd64
$ kubectl version Client Version: version.Info{Major:“1”, Minor:“15+”, GitVersion:“v1.15.8-beta.0”, GitCommit:“6c143d35bb11d74970e7bc0b6c45b6bfdffc0bd4”, GitTreeState:“archive”, BuildDate:“2020-01-02T00:00:00Z”, GoVersion:“go1.13.5”, Compiler:“gc”, Platform:“linux/amd64”}
$ docker info Containers: 6 Running: 0 Paused: 0 Stopped: 6 Images: 7 Server Version: 18.09.8 Storage Driver: overlay2 Backing Filesystem: xfs Supports d_type: true Native Overlay Diff: true Logging Driver: journald Cgroup Driver: systemd Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: /usr/libexec/docker/docker-init containerd version: runc version: ce97911e3cd37a5ce3ef98f7f1d4add21a3ac162 init version: v0.18.0 (expected: fec3683b971d9c3ef73f284f176672c44b448662) Security Options: seccomp Profile: default selinux Kernel Version: 5.3.16-300.fc31.x86_64 Operating System: Fedora 31 (Workstation Edition) OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 62.6GiB Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: true
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (8 by maintainers)
Kubectl on the host shouldn’t matter during create.
Does docker on the host have IPv6 enabled for containers? Does kind work without this config?
make sure your kubectl is at least 1.16 or better 1.17.
what are the logs if you pass e.g.
--v=5
to the kind command?