Local Kubernetes Dev — Part 15: Common problems and how to fix them

"I built the image with docker build, but in k3d it's ImagePullBackOff. How? The image exists!"

Because k3d nodes run on containerd, and it's isolated from your Docker daemon. Docker has the image, the cluster doesn't. The most disorienting moment for a k3d newcomer, and it's fixed two ways: k3d image import, or (better) a local registry with the full name k3d-registry.localhost:5000/myapp:dev in the manifest.

In the new article (part 15) — a field guide to the statuses you hit every week, all diagnosed with the same three commands:
• ImagePullBackOff / ErrImagePull (+ the k3d containerd trap);
• CrashLoopBackOff (and why logs --previous is the key);
• Pending / FailedScheduling;
• OOMKilled (137) — and the sneaky node-level OOM inside the Docker VM;
• Service is silent: a break in the Service → endpoints → Pod chain (selector / ports / readiness);
• Tilt not picking up changes;
• k3d/Docker ate the disk.

Bookmark it: https://dorokhovich.com/blog/local-k8s-troubleshooting?utm_source=devto&utm_medium=syndication&utm_campaign=local-k8s-troubleshooting