Listen to this Post
Interviewers love Docker questions, not because they want you to memorize commands, but to check:
1. Do you understand container lifecycle?
2. Can you debug production issues?
- Will you panic when a container restarts unexpectedly?
Here’s the Docker container lifecycle, explained in a way that helps you answer interview questions:
🔸 `docker create` vs `docker run`
– `docker create` builds a stopped container.
– `docker run` = `create` + start.
Interview Tip: Expect questions like “How do you create a container without starting it?”
🔸 From Running to Stopped
docker stop,docker kill, OOM kills — they all stop containers. But how they stop matters.
Interview Tip: Be ready to explain the difference between graceful (stop) vs forceful (kill) termination.
🔸 Restart Policies
- If a container crashes, should Docker auto-restart it?
Interview Tip: They may ask about `–restart=always` or when you’d not want auto-restart.
🔸 Paused State = Frozen in Time
- Containers can be paused (
docker pause) and resumed (docker unpause). Rarely used, but a good edge-case question.
Interview Tip: Interviewers love asking about corner cases. Knowing this gives you an edge.
🔸 Deleted Means Gone Forever
- Use `docker rm` to delete. But be cautious—deleted containers can’t be restarted.
Interview Tip: “What’s the difference between `stop` and rm?” — a basic but essential question.
You Should Know:
Essential Docker Commands & Debugging
1. Container Lifecycle Commands
Create but don’t start docker create --name my_container nginx Start a stopped container docker start my_container Run (create + start) docker run -d --name my_running_container nginx Stop gracefully (SIGTERM) docker stop my_running_container Force kill (SIGKILL) docker kill my_running_container Pause & Resume docker pause my_running_container docker unpause my_running_container Remove a container (must be stopped) docker rm my_container
2. Debugging & Inspecting Containers
View logs docker logs my_container Inspect container details (JSON) docker inspect my_container Check running processes inside container docker top my_container Execute a command inside a running container docker exec -it my_container /bin/bash Monitor resource usage docker stats my_container
3. Restart Policies
Always restart (even on manual stop) docker run -d --restart=always nginx Restart only on failure (exit code != 0) docker run -d --restart=on-failure:5 nginx Never restart (default) docker run -d --restart=no nginx
4. Handling OOM (Out-of-Memory) Issues
Limit container memory docker run -d -m 512m --memory-swap 1g nginx Check OOM events docker events --filter 'event=oom'
What Undercode Say:
Mastering Docker isn’t about memorizing commands—it’s about understanding how containers work under the hood. Key takeaways:
– `docker run` ≠ `docker create + start` (know the difference).
– `stop` vs `kill` (graceful vs forceful termination).
– Restart policies define resilience (critical for production).
– Debugging (logs, inspect, exec) is more valuable than syntax recall.
– OOM kills happen—always monitor resource limits.
For deeper learning, check:
Expected Output:
Sample debugging workflow docker run -d --name web_server nginx docker logs web_server docker exec -it web_server /bin/bash docker stats web_server docker stop web_server docker rm web_server
References:
Reported By: Akashsinnghh Docker – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅
