High Docker Question 156 of 221

A serving image works locally but OOMKills on Kubernetes. How do you debug?

MLOps track · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: DATA SPLIT

Train 70%Val 15%Test 15%

Fit on train, tune on val, report on test once.

Simple meaning

I would compare memory requests, model load plus thread pools, and whether local used a smaller weights file.

WHY — Docker instead of guessing?

Why interviewers care about Docker:

Docker questions separate people

who only read docs from people who shipped.

Keep it short, concrete,

and tied to MLOps work.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

1
I would compare memory
requests, model load plus thread pools, and whether local used a smaller weights file.
2
Tools like a memory
profile during a load test show whether workers times model size exceed the limit.
3
I would also check
if multiple Gunicorn workers each loaded a full copy of the network.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“Tools like a memory profile during a load test show whether workers times model ”

Break into beats

Toolslikeamemoryprofileduring

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

I would compare memory requests, model load plus thread pools, and whether local used a smaller weights file. Tools like a memory profile during a load test show whether workers times model size exceed the limit.