DEVOPSFixes
home/about

About DevOpsFixes

A running log of every DevOps problem I've hit — and exactly how I fixed it.


The story

I'm a DevOps engineer. Every week I run into something weird — a Kubernetes pod that won't start, a Terraform state that's locked, a CI pipeline that fails for no obvious reason.

For years I fixed these things, moved on, and forgot them. Then six months later I'd hit the exact same issue and waste another two hours Googling through Stack Overflow answers from 2016 and GitHub issues marked "won't fix."

So I started writing them down. Not tutorials — just the problem, the root cause, and the fix. DevOpsFixes is that notebook, made public.

What you'll find here

Every post follows the same structure — the exact error message, what's actually causing it, and the fix with copy-paste commands. No 10-minute intro, no "in this tutorial we will learn." Just the thing you need at 2am when the deployment is broken.

Problem — what broke and the error you see
Cause — why it actually happened
Fix — exact steps to resolve it

Topics covered

Kubernetes, Docker, Linux, CI/CD (GitHub Actions, Jenkins, GitLab), Terraform, AWS and general cloud infrastructure. Mostly things I use day-to-day. If a fix helped me, it ends up here.

Who it's for

DevOps engineers, SREs, platform engineers, and developers who manage their own infrastructure. If you've ever lost an hour to a cryptic error that turned out to have a three-line fix, this site is for you.

Found a fix useful?
Browse all documented fixes or search for your error.
Browse all fixes →