kind: cannot create cluster on M1 with amd64 image
What happened:
$ kind create cluster
Creating cluster "kind" ...
✓ Ensuring node image (kindest/node:v1.25.3) 🖼
✗ Preparing nodes 📦
ERROR: failed to create cluster: could not find a log line that matches "Reached target .*Multi-User System.*|detected cgroup v1"
What you expected to happen:
There are no errors and the cluster was created.
How to reproduce it (as minimally and precisely as possible):
Run on m1
Anything else we need to know?:
I found the error messages expect a cgroup v1
, but my docker uses cgroup v2
. Is it be supported now?
Environment:
- kind version: kind v0.17.0 go1.19.2 darwin/arm64
- Kubernetes version: v1.23.1
- Docker version:
Client:
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc., v0.8.2)
compose: Docker Compose (Docker Inc., v2.5.1)
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
scan: Docker Scan (Docker Inc., v0.17.0)
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 62
Server Version: 20.10.14
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: 3df54a852345ae127d1fa3092b95168e4a88e2f8
runc version: v1.0.3-0-gf46b6ba
init version: de40ad0
Security Options:
seccomp
Profile: default
cgroupns
Kernel Version: 5.10.104-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 9.952GiB
Name: docker-desktop
ID: ZWVT:2FQD:VLYG:LJNP:FTMD:43CI:TZGO:ZQMC:RAES:OXO2:6JFH:POXZ
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5000
127.0.0.0/8
Live Restore Enabled: false
- OS (e.g. from
/etc/os-release
):
$ sw_vers
ProductName: macOS
ProductVersion: 12.1
BuildVersion: 21C52
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (12 by maintainers)
we’ll roll up into #2718 for further discussion on which approach to take for mitigating or at least warning about this
v0.14.0…v0.15.0 doesn’t present much related to node bringup, there’s some changes on ZFS, and with rebooting existing nodes, and changes not related to starting clusters (like optimizing
kind load ...
).since you’re on M1, is it possible this was was #2718 ?