-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot create kind cluster with --config flag #2959
Comments
You may need to raise the amount of memory allocated for Docker Desktop in order to create a three node cluster. Have you tried/verified that you are able to create a single node cluster? That would be a good sanity check of your environment to make sure there isn't some other underlying issue. Another thing to try would be to run |
Can we see |
1.25.14 isn't a real Kubernetes version (latest is 1.25.2) This digest also doesn't appear to match any from any recent KIND releases ... what is this image? |
Oh, my bad there. That was a typo. I updated the version and tried again, but the same error. ~ ❯❯❯ docker logs 23f22a62e390
INFO: ensuring we can execute mount/umount even with userns-remap
INFO: remounting /sys read-only
INFO: making mounts shared
INFO: detected cgroup v2
INFO: clearing and regenerating /etc/machine-id
Initializing machine ID from random generator.
INFO: setting iptables to detected mode: legacy
iptables-save v1.8.7 (legacy): Cannot initialize: iptables who? (do you need to insmod?)
INFO: ensuring we can execute mount/umount even with userns-remap
INFO: remounting /sys read-only
INFO: making mounts shared
INFO: detected cgroup v2
INFO: clearing and regenerating /etc/machine-id
Initializing machine ID from random generator.
INFO: setting iptables to detected mode: legacy
iptables-save v1.8.7 (legacy): Cannot initialize: iptables who? (do you need to insmod?)
~ ❯❯❯ docker logs efd024650c25
INFO: ensuring we can execute mount/umount even with userns-remap
INFO: remounting /sys read-only
INFO: making mounts shared
INFO: detected cgroup v2
INFO: clearing and regenerating /etc/machine-id
Initializing machine ID from random generator.
INFO: setting iptables to detected mode: legacy
iptables-save v1.8.7 (legacy): Cannot initialize: iptables who? (do you need to insmod?)
INFO: ensuring we can execute mount/umount even with userns-remap
INFO: remounting /sys read-only
INFO: making mounts shared
INFO: detected cgroup v2
INFO: clearing and regenerating /etc/machine-id
Initializing machine ID from random generator.
INFO: setting iptables to detected mode: legacy
iptables-save v1.8.7 (legacy): Cannot initialize: iptables who? (do you need to insmod?)
~ ❯❯❯ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
23f22a62e390 kindest/node:v1.25.2 "/usr/local/bin/entr…" 55 seconds ago Exited (1) 51 seconds ago kind-worker2
cbedeaa30970 kindest/node:v1.25.2 "/usr/local/bin/entr…" 55 seconds ago Exited (1) 51 seconds ago kind-worker
efd024650c25 kindest/node:v1.25.2 "/usr/local/bin/entr…" 55 seconds ago Exited (1) 51 seconds ago kind-control-plane |
Is this the arm64 image or amd64? the fact that we can't detect or use iptables smells like wrong architecture |
|
My bad! That was the real issue! ~ ❯❯❯ kubectl get nodes
NAME STATUS ROLES AGE VERSION
kind-ha-control-plane Ready control-plane 38s v1.25.2
kind-ha-worker Ready <none> 18s v1.25.2
kind-ha-worker2 Ready <none> 18s v1.25.2 |
What happened:
I am trying to make my kind environment declarative and creating a kind config to create my cluster. Cluster creation with
--config
consistently fails, whereas without it succeeds.What you expected to happen:
Kind cluster should be able to create with config provided to it.
How to reproduce it (as minimally and precisely as possible):
The config that i am creating:
the command that i'm using:
Anything else we need to know?:
Environment:
kind version
):~ ❯❯❯ kind version kind v0.16.0 go1.19.1 darwin/arm64
kubectl version
):docker info
):/etc/os-release
): macOS Monterey M1 macbook pro#2959 (comment)
The text was updated successfully, but these errors were encountered: