Files
kubesolo-os/init/lib/80-containerd.sh
Adolfo Delorenzo e372df578b feat: initial Phase 1 PoC scaffolding for KubeSolo OS
Complete Phase 1 implementation of KubeSolo OS — an immutable, bootable
Linux distribution built on Tiny Core Linux for running KubeSolo
single-node Kubernetes.

Build system:
- Makefile with fetch, rootfs, initramfs, iso, disk-image targets
- Dockerfile.builder for reproducible builds
- Scripts to download Tiny Core, extract rootfs, inject KubeSolo,
  pack initramfs, and create bootable ISO/disk images

Init system (10 POSIX sh stages):
- Early mount (proc/sys/dev/cgroup2), cmdline parsing, persistent
  mount with bind-mounts, kernel module loading, sysctl, DHCP
  networking, hostname, clock sync, containerd prep, KubeSolo exec

Shared libraries:
- functions.sh (device wait, IP lookup, config helpers)
- network.sh (static IP, config persistence, interface detection)
- health.sh (containerd, API server, node readiness checks)
- Emergency shell for boot failure debugging

Testing:
- QEMU boot test with serial log marker detection
- K8s readiness test with kubectl verification
- Persistence test (reboot + verify state survives)
- Workload deployment test (nginx pod)
- Local storage test (PVC + local-path provisioner)
- Network policy test
- Reusable run-vm.sh launcher

Developer tools:
- dev-vm.sh (interactive QEMU with port forwarding)
- rebuild-initramfs.sh (fast iteration)
- inject-ssh.sh (dropbear SSH for debugging)
- extract-kernel-config.sh + kernel-audit.sh

Documentation:
- Full design document with architecture research
- Boot flow documentation covering all 10 init stages
- Cloud-init examples (DHCP, static IP, Portainer Edge, air-gapped)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-11 10:18:42 -06:00

23 lines
794 B
Bash
Executable File

#!/bin/sh
# 80-containerd.sh — Start containerd (bundled with KubeSolo)
#
# NOTE: KubeSolo typically manages containerd startup internally.
# This stage ensures containerd prerequisites are met.
# If KubeSolo handles containerd lifecycle, this stage may be a no-op.
# Ensure containerd state directories exist
mkdir -p /run/containerd
mkdir -p /var/lib/containerd
# Ensure CNI directories exist
mkdir -p /etc/cni/net.d
mkdir -p /opt/cni/bin
# If containerd config doesn't exist, KubeSolo will use defaults
# Only create a custom config if we need to override something
if [ -f /etc/kubesolo/containerd-config.toml ]; then
log "Using custom containerd config from /etc/kubesolo/containerd-config.toml"
fi
log_ok "containerd prerequisites ready (KubeSolo manages containerd lifecycle)"