When a container or Kubernetes node fails, the cause may be an ordinary Linux problem: a process has stopped, a disk is full or a file cannot be read. Linux is the operating system beneath many servers and container hosts, so these skills make later Kubernetes problems easier to understand.

Start with a disposable virtual machine. Learn to inspect processes, files, permissions and network connections, then practice fixing one deliberate failure. The old course outline below remains a guide to subjects rather than a currently hosted course.

Linux skills for Kubernetes operations

Learn processes, permissions, filesystems, networking, DNS, package management and logs before treating a node as an opaque appliance. Practice finding the cause of a failed service, full filesystem and unreachable endpoint in a disposable virtual machine.

Then connect those concepts to namespaces, cgroups, container runtimes and storage mounts. Modern node operating systems can restrict direct package changes, so distinguish general Linux knowledge from the supported maintenance method of a specific distribution. The historical course outline does not imply that its Vagrant or Docker setup remains the best current default.

The original record

Historical Kubedex content

Preserved for context. Commands, versions, prices and results below reflect the original research.

Sources & further reading

  1. Kubernetes node runtime prerequisites
  2. Recovered historical source

Spotted something that needs another look?

Help improve this page →