⚡ ~/naveed Interview Prep
⚡ Portfolio Home ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 998+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
Senior DevOps / SRE [L2] Docker Production Scenario [L2]

Q: A container is consuming 100% CPU. How do you limit it without restarting?

docker update --cpus="1.5" <container> — limit to 1.5 CPU cores. Also --memory="512m" for memory limit. For Kubernetes, update the resour...

#Docker #Docker #L2 #Containers #Linux
🎙️ Candidate Opening & Architectural Context
""During an image optimization initiative across our services, we solved this exact problem. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement

🛠️ Production Runbook & Step-by-Step Resolution

1️⃣

Production Solution & Architecture

docker update --cpus="1.5" — limit to 1.5 CPU cores. Also --memory="512m" for memory limit. For Kubernetes, update the resource limits in the pod spec and trigger a rolling restart.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: docker update --cpus="1.5" — limit to 1.5 CPU cores. Also --memory="512m" for memory limit. For Kubernetes, update the resource l."
⚡ 60-Second Elevator Pitch Talking Points
  • Immediate Triage: docker update --cpus="1.5" — limit to 1.5 CPU cores. Also --memory="512m" for memory limit. Fo
  • Run targeted verification commands before modifying configuration.
  • Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement
Want more Docker scenarios?
Explore our complete collection of scenario-based Docker interview runbooks.
Browse All Docker Questions →

📚 Related Production Scenarios in Docker