Running Kubernetes on Apple Silicon: Setup, Gotchas, Recovery

Thu, 07 May 2026 00:00:00 +0000

A minikube cluster on Apple Silicon looks like a pure Kubernetes problem until the first Docker Desktop crash. The failure modes that bite hardest on M-series Macs live one layer below the cluster: in Docker Desktop’s memory allocator, in QEMU’s address-space layout, and in the destructive default of minikube delete. None of these are mentioned in the standard minikube setup guide, and all three will eat real workload state when they fire. This is the operational layer on top of minikube setup and drivers and ARM64 K8s images — the host-side discipline that keeps the cluster alive.

Single-Node Kubernetes Disaster Recovery: Backups That Survive a Wiped Docker VM

Thu, 07 May 2026 00:00:00 +0000

A single-node minikube cluster on Docker Desktop runs the entire control plane, kubelet, every PVC, every Secret, and the container image cache inside one VM whose disk is one file: ~/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw on macOS. When that file is lost or corrupted, every piece of cluster state goes with it in a single event. There is no “node failure vs storage failure” distinction to design around. Every backup strategy that assumes those are separable does not apply.

Docker-Desktop on Agent Zone

Running Kubernetes on Apple Silicon: Setup, Gotchas, Recovery

Single-Node Kubernetes Disaster Recovery: Backups That Survive a Wiped Docker VM