kind failed when create a cluster

[marioidival]

What happened:

I'm try to create a cluster with kind

create-cluster-failed.tar.gz

What you expected to happen:
A cluster created

How to reproduce it (as minimally and precisely as possible):
kind create cluster --name lm-lm

Anything else we need to know?:

Environment:

• kind version: (use kind version): kind v0.26.0 go1.23.4 linux/amd6
• Runtime info: (use docker info, podman info or nerdctl info):

Client: Docker Engine - Community
Version:    27.4.1
Context:    default
Debug Mode: false
Plugins:
 buildx: Docker Buildx (Docker Inc.)
   Version:  v0.19.3
   Path:     /usr/libexec/docker/cli-plugins/docker-buildx
 apparmor
 seccomp
  Profile: builtin
 cgroupns
Kernel Version: 6.8.0-51-generic
Operating System: Ubuntu 24.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 31.21GiB
Name: homelab
ID: 813cbbeb-64ff-4e66-aa42-d99bcc67e9bd
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

• OS (e.g. from /etc/os-release):

NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

• Kubernetes version: (use kubectl version):

Client Version: v1.32.0
Kustomize Version: v5.5.0

• Any proxies or other special environment settings?:

[aojea]

is there any special in this environment?

        "Error": "failed to create task for container: Unimplemented: failed to start shim: start failed: unsupported shim version (3): not implemented",

a quick search points to containerd 2.0 containerd/containerd#10984

[marioidival]

Hello @aojea no, I've just tried to run as usual.

[stmcginnis]

The docker info output seems to be missing quite a bit. Here's the full output from the logs to make it easier for others to review it:

Client: Docker Engine - Community
 Version:    27.4.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.19.3
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.32.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 5
 Server Version: 27.4.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 88bf19b2105c8b17560993bee28a01ddc2f97182
 runc version: v1.2.2-0-g7cb3632
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.8.0-51-generic
 Operating System: Ubuntu 24.04.1 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 31.21GiB
 Name: homelab
 ID: 813cbbeb-64ff-4e66-aa42-d99bcc67e9bd
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Only difference I see compared to my own environment is the storage driver being overlay2 vs mine with overlayfs.

As @aojea pointed out, this system isn't even able to start the container. That's a pretty basic foundational requirement, and not kind specific. Are you able to successfully do something like docker run hello-world?