-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
kind v0.10 does not work with Kubernetes v1.21 #2236
Comments
this is probably because of alpine using openrc instead of systemd. that should already be fixed at HEAD by #2091 |
Thanks @BenTheElder. I updated to the main branch and it's working without a problem. Any Idea on when that is going to make it into a release? |
O(soon) ™️, mostly want to finish #2176 |
it works with 1d4788d kubernetes version v1.20
|
We know that the cgroups fix worked on a different systemdless distro from another user but not this one. We'll need more data. If you run a privileged container and dump the mounts and cgroups tree what do you get? |
@lazedo please file another bug with your info. I'm going to close this one as we solved OPs problem for the original configuration provided. |
Ahhh rereading this it's the same distro same version just a newer kind commit / kubernetes. My apologies. We frequently have issues fragmenting into 10 different actual problems from different users woven into the same issue and I've gotten too quick to break them up. |
One more here #166 (comment) but we don't know anything about the host other than probably arm64. |
@BenTheElder the host in my test for alpine 3.13.5 is amd64 (actually a vm inside hyper-v but worked until now). other previleged containers work such as |
Interesting thanks, dind is slightly slightly simpler as it doesn't need to make kubelet happy.
We need some info like this to determine the mount structure being used, this sounds wrong. Eg. docker should not be mounting you can see more about what we need to do here
|
Same issue here: EDIT: added docker info output
|
@lasdolphin I think you were using v1.21 image with kind v0.10.0? that's a different problem and isn't expected to work and will be fixed by upgrading to v0.11 #166 (comment) which is release-in-progress as I type. #2236 (comment) also suggests that is what @spam-n-eggs's issue was. @lazedo were you also trying to run Kubernetes v1.21.0+ with kind v0.10? That does not work due to a breaking change in kubernetes/kubeadm, it's fixed in the latest kind sources which are receiving a tagged release currently. If not: please file a new issue with your details. |
@BenTheElder i was running |
https://github.com/kubernetes-sigs/kind/releases/tag/v0.11.0#contributors is out @lazedo I think we need a separate issue to track your problem as we fixed the original here and it's not clear if they were related, but we should cross reference them. |
What happened: When creating the default
kind
cluster, the docker container started but exited immediatelyFrom
kind export logs
:What you expected to happen: The control plane to start and create the kubernetes cluster
How to reproduce it (as minimally and precisely as possible): On a fresh install of Alpine 3.13, with docker installed, download the latest version of kind via go get, and run
kind create cluster
Anything else we need to know?: Could this be the same issue as #2228 ?
Environment:
kind version
): kind v0.10.0 go1.15.10 linux/amd64kubectl version
):docker info
):/etc/os-release
):The text was updated successfully, but these errors were encountered: