⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ 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) →
← Back to All Docker & Containers Interview Questions Scenario 91 of 159 in Docker & Containers
Staff SRE / Principal Architect [L3] Docker Must enable BuildKit Staff SRE Scenario [L3]
🎯 Target Role / Context: Docker Scenario #92 (L3) · Must enable BuildKit

Q: Your team wants to implement live migration of a running Docker container from one host to another without stopping it, similar to VM live migration. Is this possible with Docker? What technology enables it?

Docker has experimental support for checkpoint and restore using CRIU (Checkpoint/Restore In Userspace).

#Docker #Must enable BuildKit #L3 #Containers #Linux #Terraform State
🎙️ Candidate Opening & Architectural Context
""Container stability relies on clean signal handling (SIGTERM vs SIGKILL) and immutable image tagging. The interviewer is testing: CRIU (Checkpoint/Restore in Userspace), container migration limitations.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? KodeKloud's Docker Certified Associate (DCA) Hands-On Lab Course covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "Container stability relies on clean signal handling (SIGTERM vs SIGKILL) and immutable image tagging. The interviewer is testing: CRIU (Checkpoint/Restore in Userspace), container migration limitations.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

Docker has experimental support for checkpoint and restore using CRIU (Checkpoint/Restore In Userspace). CRIU freezes a running process, serializes its entire state (memory, registers, open files, sockets, timers) to disk, and can restore it later — even on a different host.

  • Checkpoint: docker checkpoint create checkpoint1
  • Transfer the checkpoint data and container filesystem to the target host.
  • Restore: docker start --checkpoint checkpoint1
2️⃣

Remediation & Permanent Safeguards

Workflow: *Limitations:* This feature is experimental and not production-ready. Open network connections break (TCP state doesn't survive cross-host migration). External storage must be shared (e.g., NFS). GPU state, complex IPC, and certain kernel features aren't fully supported. For production workloads, Kubernetes pod rescheduling with graceful shutdown/startup is the practical alternative.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Checkpoint: docker checkpoint create checkpoint1."
⚡ 60-Second Elevator Pitch Talking Points
  • Checkpoint: docker checkpoint create checkpoint1
  • Transfer the checkpoint data and container filesystem to the target host.
  • Restore: docker start --checkpoint checkpoint1
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Structuring Dockerfile instructions inefficiently by copying app source before package manifests when configuring team wants implement Copying code before package manifests (package.json, go.mod, requirements.txt) invalidates the build cache on every commit, forcing slow full reinstalls.
  2. Neglecting the PID 1 process reap problem and omitting proper SIGTERM signal forwarding when configuring team wants implement If an application runs as PID 1 without an init system (like tini), it fails to reap zombie child processes and ignores SIGTERM signals, causing unclean 10s timeouts.
  3. Assembling single-stage images containing compilers, build SDKs, and header files in production when configuring team wants implement Single-stage builds bloat image size by gigabytes and expose extensive package vulnerabilities; multi-stage builds isolate artifacts into minimal distroless images.
  4. Confusing container port forwarding on bridge networks with unisolated host networking mode when configuring team wants implement Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.
Advertisement
Want more Docker & Containers scenarios?
Explore our complete collection of scenario-based Docker & Containers interview runbooks.
Browse All Docker & Containers Questions →