-
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
Creating cluster fails in M2 Macbook #3621
Comments
I hadn't noticed the kubelet log entry before: "command failed" err="failed to run Kubelet: could not detect clock speed from output That seems very odd. But looking at the |
Thanks @stmcginnis! |
google/cadvisor#2237 (comment) Is there any chance you have DOCKER_DEFAULT_PLATFORM set? #2718 |
Based on the logs tarball I see AMD64 images, so I'm assuming this is a duplicate of #2718 Docker's "cross platform images" only use partial emulation that cannot run a workload like Kubernetes. We can only run an arm64 kind cluster on an arm64 VM/host. (In theory a full AMD64 VM should be able to run AMD64 nodes). #2718 for discussing thoughts on what we might do to warn or block this setting. |
Hello @BenTheElder. Yes, I have |
Yes, or only set it when running certain other commands, or set it to See more discussion in #2718 /triage duplicate |
@BenTheElder: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What happened:
kind create cluster
fails in an M2 Macbook. See logs.What you expected to happen:
Kind cluster correctly created.
How to reproduce it (as minimally and precisely as possible):
kind create cluster
Anything else we need to know?:
Environment:
kind version
): kind v0.23.0 go1.22.3 darwin/arm64docker info
,podman info
ornerdctl info
):/etc/os-release
):kubectl version
):The text was updated successfully, but these errors were encountered: