Container-Optimized Operating Systems: What Makes Them Different
Read-only /usr, atomic A/B updates, and boot-time configuration: how container-optimized operating systems differ from a conventional distro with Docker.
NetBay journal
Practical guides for Linux, containers, CI/CD, self-hosting, and running VPS infrastructure from Netbay Engineering.
499 articles · 24 topics
Read-only /usr, atomic A/B updates, and boot-time configuration: how container-optimized operating systems differ from a conventional distro with Docker.
Go past a single healthcheck: layered probes, readiness vs liveness, and systemd watchdogs for containers that repair themselves.
The .github directory is repo policy as code — issue forms, workflows, owners files, and community defaults — and org-level repos inherit it everywhere.
Cache dependencies and build outputs with correct keys so every run is fast and never silently stale.
Watch disk and CPU on a VPS and let the agent run only allowlisted fixes such as journal vacuum or nginx reload, logging every action it takes.
Log tokens, encode_ms, generate_ms, and RSS on every CPU inference request so you see saturation and OOM risk before the OOM killer ever fires.
Deploy unattended-upgrades on Debian or dnf-automatic on Rocky so security patches install themselves without breaking your running services.
Read-only roots, atomic updates, and containerized apps: how Silverblue and MicroOS change patching, deployment, and what a VPS admin must unlearn.
Steal this practical CI/CD pipeline template: lint, test, build, scan, and deploy in workflows your team can copy and adapt today.
Guard infrastructure changes with four gates: lint the code, validate syntax, dry-run against real state, and gate applies on the result.
Protect a small Kubernetes cluster with etcd snapshots plus manifest exports, and restore them on a fresh k3s install.
Treat each VPS as a line item in INR: right-size roles, delay splits until SLOs demand them, and turn idle nodes off instead of overbuying reserved capacity.