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
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
Mar 03 11:03:27 kubedee-v1-10-0-beta-1-worker-46igat kubelet[850]: W0303 11:03:27.114392 850 fs.go:539] stat failed on /dev/loop1 with error: no such file or directory
Mar 03 11:03:27 kubedee-v1-10-0-beta-1-worker-46igat kubelet[850]: F0303 11:03:27.114402 850 kubelet.go:1356] Failed to start ContainerManager failed to get rootfs info: failed to get device for dir "/var/lib/kubelet": could not find device with major: 0, minor: 110 in cached partitions map
b259543985 collect ephemeral storage capacity on initialization
68dadcfd15 Make eviction manager work with CRI container runtime.
With b259543985 the kubelet fails to start when RootFsInfo returns an error where before it did only log a message. For example from a v1.9.3 kubedee cluster:
Mar 03 11:43:37 kubedee-v1-9-3-worker-ja6ihf kubelet[763]: E0303 11:43:37.233591 763 container_manager_linux.go:583] [ContainerManager]: Fail to get rootfs information failed to get device for dir "/var/lib/kubelet": could not find device with major: 0, minor: 142 in cached partitions map
shows two commits:
With b259543985 the kubelet fails to start when
RootFsInfo
returns an error where before it did only log a message. For example from a v1.9.3 kubedee cluster:Two old issues discussing the problem:
..and the corresponding patches:
In kubedee
RootFsInfo
fails because/dev/loopX
(the mount source of/var/lib/kubelet
) was not mounted into the container up until now.The text was updated successfully, but these errors were encountered: