36 articles tagged with Debugging.
A Pending pod means the scheduler couldn't place it or the node couldn't start it. Here's how to read the events and clear the eight causes we hit most.
You run the container, check docker ps, and it's already gone. Nine times out of ten it's PID 1 doing its job. Here's how to read it.
You run docker run, and it refuses to bind port 8080. Something already owns that port. Here is how to find the holder and get your container up.
A pod dies, restarts, dies again, and the events say OOMKilled. Here is what exit code 137 actually means and how to stop the loop for good.
The daemon socket is owned by root, and your user isn't allowed to touch it. Here's the fix, and why the obvious one is a security smell.
CrashLoopBackOff means your container keeps dying on startup and Kubernetes keeps restarting it slower each time. Here's the diagnosis flow we actually use.
A merge conflict isn't Git breaking. It's Git asking you a question it can't answer alone. Here's how to answer it calmly, every time.
The daemon error almost never means Docker is broken. Nine times out of ten it's a stopped service, a stale context, or a wrong env var. Here's the checklist.
Your pod is stuck because the node can't pull the image. Here's how to read the events, find the real reason, and fix each one fast.
When a service is slow and every dashboard looks green, bpftrace lets you watch the kernel directly. These one-liners found our tail latency.
When the service is slow and the network is suspect, these are the tools we reach for, in this order, with the exact flags that find the answer.
bpftrace one-liners replace strace, perf top, and a half-dozen ad-hoc debugging scripts. The patterns that actually earn their place when you're troubleshooting at 2 AM.
