-
Notifications
You must be signed in to change notification settings - Fork 820
Description
To be honest it seems some configuration error on my side, but I could not find anything related in the documentation, repo issues and over the internet
Summary
I have a microk8s installation in a server. While it has free disk space, some containers fail with "no space left on device" for "kube-api-access" volumes.
I deleted and recreated some containers, which made this issue started happening. Container stays on ContainerCreating with event:
Warning FailedMount 84s (x4 over 7m30s) kubelet (combined from similar events): MountVolume.SetUp failed for volume "kube-api-access-w8g5f" : write /var/snap/microk8s/common/var/lib/kubelet/pods/39d37f2c-503a-4700-85b4-05726ec7e08a/volumes/kubernetes.io~projected/kube-api-access-w8g5f/..2025_02_18_04_24_58.3702524494/namespace: no space left on device
What Should Happen Instead?
Container should be created normally
Reproduction Steps
I'm not so sure on how to reproduce this issue, as the first cluster setup worked fine, and only when I deleted and recreated containers over time I got this issue. The configuration files for this server are public, and, for example, rancher is failing to be recreated with error above.