Q: You need to debug a broken Docker image, but the container instantly crashes upon starting, so you can't `docker exec` into it. You want to inspect the actual files inside the image layer directly on the Linux host disk. Where in the filesystem do you look?
Docker does not store containers as large VM .vmdk files. It uses a Union Filesystem (typically overlay2).
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: The overlay2 filesystem, container storage drivers.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Docker does not store containers as large VM .vmdk files. It uses a Union Filesystem (typically overlay2).
- Run
docker inspect. - Look at the
GraphDriver.Data.MergedDirattribute. - CD into that absolute path (
/var/lib/docker/overlay2/abc123.../merged).
Remediation & Permanent Safeguards
All image layers and actively mutated container filesystems exist as raw directories located in /var/lib/docker/overlay2/. To find the exact directory for the broken image: There, you will see a perfect, unbooted replica of the container's root filesystem ( /etc, /usr, /var). You can use standard Linux tools (cat, vim) directly on the host to debug the bad config file causing the crash.
- Run docker inspect .
- Look at the GraphDriver.Data.MergedDir attribute.
- CD into that absolute path (/var/lib/docker/overlay2/abc123.../merged).
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring need debug broken SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring need debug broken
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring need debug broken Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring need debug broken
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).