Closed fdawg4l closed 1 year ago
As you can see from the output you posted, your host filesystem doesn't have enough free disk space, which makes kubelet
think it doesn't have disk space to launch a pod. When running in a container mode, your host filesystem becomes what kubelet
sees as the disk. When running in QEMU/VM mode, Talos will use whatever space is allocated to it.
@smira thanks for taking a look. Right, kubelet claims there’s not enough space. I see 13.5Gb free. How much free space is required to use sidero to bootstrap a cluster?
It's not sidero, but rather kubelet default settings:
evictionHard is a map of signal names to quantities that defines hard eviction thresholds. For example: {"memory.available": "300Mi"}. To explicitly disable, pass a 0% or 100% threshold on an arbitrary resource. Default: memory.available: "100Mi" nodefs.available: "10%" nodefs.inodesFree: "5%" imagefs.available: "15%"
Hi,
I'm following the Getting Started guide's Prerequisite: Kubernetes section and am trying to get the local docker cluster going and it's timing out. It looks like it's becuase the container is out of space, but it looks like there's plenty of space. Am I missing something?