-
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
KIND kubelet fails to start #3664
Comments
/remove-kind bug Can you check if |
I dont see it set. Should I set it |
unset is preferable, so we can just use the docker default (which matches the host), but if it is set it should match the host platform, which in your case is not amd64 see #2718 |
yea it is unset. It should be using the docker default. NOTE: I tested other docker containers (like hello-world) and they worked fine. |
Based on the logs it looks like #2718, this appears to be an amd64 image on an arm64 host. Maybe the image was already pulled as amd64 previously? |
Ive cleared all the images and containers out of docker and tried to run on a "clean" docker but still hit same issue. |
one thing to note compaired to #2718 is my install passes the |
Adding my cluster yaml for additional details
|
From images.log we can see amd64 images preloaded into this node image, indicating it's an amd64 image. This still looks like a variation on #2718 Can you try explicitly using the arm64 image?
You can use: |
Better yet also with It still looks like something is causing the wrong architecture to be run, and kind doesn't do anything this internally, that would be docker. |
Ok it created successfully with those changes. But I wonder why it was picking up the wrong arch? |
That env may be set or there may be some other related docker setting set. Docker sort of supports cross-platform image running but the way it does it is not sufficient to run something like Kubernetes. If you figure out what setting this is overriding please let us know, I'm not aware of another option like |
What happened:
command
kind create cluster
fails at theStarting control-plane
step. Prints out an error about the kubelet not being healthy. The error logs show an issue about the clock speed verification:failed to run Kubelet: could not detect clock speed from output:
What you expected to happen:
Kind cluster to be created successfully
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
error logs: 537174967.zip
Environment:
kind version
): kind v0.23.0 go1.22.3 darwin/arm64docker info
,podman info
ornerdctl info
):/etc/os-release
): OSXkubectl version
): Client Version: v1.30.0Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The text was updated successfully, but these errors were encountered: