You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened: When creating a cluster, starting the control plane failed.
What you expected to happen: Cluster created successfully.
How to reproduce it (as minimally and precisely as possible): Run kind create cluster
Anything else we need to know?:
I'm running Fedora 35 with luks encrypted btrfs.
There appears to be an issue with ContainerManager in the kubelet.log:
Nov 26 03:51:21 kind-control-plane kubelet[978]: W1126 03:51:21.216180 978 fs.go:588] stat failed on /dev/mapper/luks-0b25d656-ca59-4fa3-8470-dcb0752b7751 with error: no such file or directory
Nov 26 03:51:21 kind-control-plane kubelet[978]: E1126 03:51:21.216207 978 kubelet.go:1384] "Failed to start ContainerManager" err="failed to get rootfs info: failed to get device for dir \"/var/lib/kubelet\": could not find device with major: 0, minor: 39 in cached partitions map"
What happened: When creating a cluster, starting the control plane failed.
What you expected to happen: Cluster created successfully.
How to reproduce it (as minimally and precisely as possible): Run
kind create cluster
Anything else we need to know?:
I'm running Fedora 35 with luks encrypted btrfs.
There appears to be an issue with ContainerManager in the kubelet.log:
Additional logs: https://gist.github.com/ukazap/13acef5eebb8aa06413bc58698e7426e
Environment:
kind version
): kind v0.11.1 go1.16.4 linux/amd64kubectl version
): v1.22.4DockerPodman version: (usedocker info
): 3.4.2/etc/os-release
): Fedora 35The text was updated successfully, but these errors were encountered: