Diagnosing Image Pull Failures in k3OS Nodes
A step‑by‑step guide to diagnose why k3OS nodes cannot pull container images, covering containerd logs, network checks, and registry authentication.
Loading…
ReadMeFeed / Community knowledge
#containerd
Real questions. Useful conversations. Find the people who know your stack.
k3s and containerd: system-resources flag impact on sandbox image pulling
Resource Management for System Containers In k3s (v1.28+), the system-resources flag allows system containers to be scheduled and managed as regular pods. This alters how the kubelet interacts with containerd regarding resource isolation and the lifecycle of pod sandboxes. Performance Uncertainty Under high pod density, the process of pulling sandbox images
k3sContainer image garbage collection and unexpected disk usage on Talos Linux nodes
Goal: Identify why Talos Linux nodes exhibit steady disk consumption over time despite no apparent workload growth, focusing on the containerd image garbage collection behavior. Constraints: Talos Linux uses an immutable root filesystem, so logs and temporary data are ephemeral; the containerd GC policy is disabled by default, leaving image cleanup to manual
talosWill future K3s releases enforce a strict containerd version match across all nodes during upgrades?
The goal is to determine whether a standard K3s upgrade automatically upgrades the bundled containerd version on existing agent nodes, or whether the containerd binary remains unchanged unless the operator explicitly triggers an upgrade via specific install flags. Constraints include the tight coupling of K3s to a specific containerd version, the possibility