Debugging Go: from zero to Kubernetes - Michele Caci
summary
Step‑by‑step guide to use Delve to inspect Go programs locally, inside Docker, and inside Kubernetes: compile and start Delve with dlv debug main.go or use dlv exec / attach / dlv test on a PID; run a separate debugger container with Docker flags --pid and --cap-add=SYS_PTRACE to let the debugger see and trace the app process; avoid permanently shipping the ~500MB debugger image alongside a ~10MB app by launching an ephemeral container via kubectl debug --image=... --target=... --profile=Debug and then attach dlv to debug.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 1:06Talk overview and goals
- 2:52What is debugging
- 6:23Debugging tools overview
- 8:53Debugging Go locally with Delve
- 10:37Debugging Go in Docker containers
- 17:21Debugging Go in Kubernetes
- 23:26Summary and key takeaways
- 26:14Q&A session
related talks
40mDebugging in Golang Apps Inside K8s Environment
34mDebugging at Scale in Production - Deep into Your Containers with Kubectl Debug
01h 00mDebug like a pro on Kubernetes
35mThe Art of Debugging Inside K8s Environment
24mDebugging at Scale in Production - Deep into your Containers
53mDebugging Go Applications
32mSquash: A Debugger for Kubernetes Apps
35mA story about debugging of one Go application