k3d/docs/faq.md

FAQ / Nice to know

• As @jaredallard pointed out, people running k3d on a system with btrfs, may need to mount /dev/mapper into the nodes for the setup to work.

  • This will do: k3d create -v /dev/mapper:/dev/mapper
  • An additional solution proposed by @zer0def can be found in the examples section (Running on filesystems k3s doesn't like (btrfs, tmpfs, …))

• Pods go to evicted state after doing X

  • Related issues: #133 - Pods evicted due to NodeHasDiskPressure (collection of #119 and #130)
  • Background: somehow docker runs out of space for the k3d node containers, which triggers a hard eviction in the kubelet
  • Possible fix/workaround by @zer0def:
    • use a docker storage driver which cleans up properly (e.g. overlay2)
    • clean up or expand docker root filesystem
    • change the kubelet's eviction thresholds upon cluster creation: k3d create --agent-arg '--kubelet-arg=eviction-hard=imagefs.available<1%,nodefs.available<1%' --agent-arg '--kubelet-arg=eviction-minimum-reclaim=imagefs.available=1%,nodefs.available=1%'