⚡ ~/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 142 of 159 in Docker & Containers
Senior DevOps Engineer Docker Container Runtime & Systems Engineering Production Scenario
🎯 Target Role / Context: Principal Docker Architect / Staff SRE Scenario

Q: A junior engineer executed `docker system prune -a --volumes -f` on a staging server to free up disk space, accidentally deleting production-mirror database volumes and wiping uncommitted test databases. On other CI nodes, unmaintained Docker hosts frequently run out of disk space due to hundreds of gigabytes of dangling images and BuildKit cache layers. You must design an automated, safe maintenance strategy that prunes stale resources using age filters without risking persistent volumes.

Design and automate recurring Docker host cleanup workflows. Use docker system prune, filters (until), BuildKit garbage collection, and safeguard stateful named volumes against accidental deletion.

#Docker #Linux #SRE #Storage #Maintenance
🎙️ Candidate Opening & Architectural Context
"Design and automate recurring Docker host cleanup workflows. Use docker system prune, filters (until), BuildKit garbage collection, and safeguard stateful named volumes against accidental deletion."
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: Design and automate recurring Docker host cleanup workflows. Use docker system prune, filters (until), BuildKit garbage collection, and safeguard stateful named volumes against accidental deletion.

Step 1

Analyze the Scope and Risks of Prune Subcommands

Understand command scopes: docker image prune removes dangling () images. docker container prune cleans stopped containers. docker system prune -a removes all unused images (not just dangling ones). Adding --volumes destroys all anonymous and unused named volumes, posing catastrophic data loss risks.

<!-- Prune Command Danger Levels -->
SAFE:        docker image prune                                (Removes dangling layers only)
CONTROLLED:  docker system prune --filter "until=168h"         (Removes stopped containers & untagged images > 7 days old)
DANGEROUS:   docker system prune -a                            (Removes ALL images not actively running!)
CATASTROPHIC: docker system prune -a --volumes                 (Destroys all unused persistent volumes!)
Pro Tip: Analyze the Scope and Risks of Prune Subcommands
Step 2

Implement Age-Filtered Maintenance with --filter until

Always qualify automated pruning scripts with the until filter (e.g., until=72h or until=168h), ensuring that recently stopped containers and recently downloaded base images are preserved for developer cache.

# Prune stopped containers older than 3 days
docker container prune --filter "until=72h" -f

# Prune unused images created more than 7 days ago (without touching volumes)
docker image prune -a --filter "until=168h" -f
Pro Tip: Implement Age-Filtered Maintenance with --filter until
Advertisement
Step 3

Configure Built-in BuildKit Garbage Collection in daemon.json

Rather than relying on manual cron jobs, configure BuildKit's native garbage collector in /etc/docker/daemon.json to enforce strict disk storage ceilings.

cat <<EOF | sudo tee /etc/docker/daemon.json
{
  "builder": {
    "gc": {
      "enabled": true,
      "defaultKeepStorage": "20GB",
      "policy": [
        {"keepBytes": 10737418240, "all": false},
        {"keepBytes": 21474836480, "all": true}
      ]
    }
  }
}
EOF
Pro Tip: Configure Built-in BuildKit Garbage Collection in daemon.json
Step 4

Deploy Automated systemd Timer for Routine Host Hygiene

Create a hardened systemd service and timer running weekly that safely trims orphaned build layers and dangling images while strictly excluding --volumes.

# /etc/systemd/system/docker-prune.service
[Unit]
Description=Safe Docker Host Prune
[Service]
Type=Oneshot
ExecStart=/usr/bin/docker system prune -f --filter "until=168h"
Pro Tip: Deploy Automated systemd Timer for Routine Host Hygiene
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Never use --volumes in automated pruning scripts. Safe host maintenance relies on age-based filters (--filter until=168h) and native BuildKit garbage collection policies in daemon.json to keep disk usage bounded without threatening persistent data."
⚡ 60-Second Elevator Pitch Talking Points
  • W
  • e
  • p
  • r
  • e
  • v
  • e
  • n
  • t
  • e
  • d
  • d
  • i
  • s
  • k
  • e
  • x
  • h
  • a
  • u
  • s
  • t
  • i
  • o
  • n
  • a
  • c
  • r
  • o
  • s
  • s
  • 2
  • 0
  • 0
  • b
  • u
  • i
  • l
  • d
  • n
  • o
  • d
  • e
  • s
  • w
  • h
  • i
  • l
  • e
  • e
  • l
  • i
  • m
  • i
  • n
  • a
  • t
  • i
  • n
  • g
  • a
  • c
  • c
  • i
  • d
  • e
  • n
  • t
  • a
  • l
  • d
  • a
  • t
  • a
  • l
  • o
  • s
  • s
  • b
  • y
  • d
  • e
  • p
  • l
  • o
  • y
  • i
  • n
  • g
  • a
  • s
  • t
  • r
  • i
  • c
  • t
  • p
  • r
  • u
  • n
  • i
  • n
  • g
  • p
  • o
  • l
  • i
  • c
  • y
  • .
  • W
  • e
  • b
  • a
  • n
  • n
  • e
  • d
  • t
  • h
  • e
  • `
  • -
  • -
  • v
  • o
  • l
  • u
  • m
  • e
  • s
  • `
  • f
  • l
  • a
  • g
  • i
  • n
  • s
  • c
  • r
  • i
  • p
  • t
  • s
  • ,
  • e
  • n
  • a
  • b
  • l
  • e
  • d
  • B
  • u
  • i
  • l
  • d
  • K
  • i
  • t
  • '
  • s
  • n
  • a
  • t
  • i
  • v
  • e
  • 2
  • 0
  • G
  • B
  • g
  • a
  • r
  • b
  • a
  • g
  • e
  • c
  • o
  • l
  • l
  • e
  • c
  • t
  • i
  • o
  • n
  • i
  • n
  • `
  • d
  • a
  • e
  • m
  • o
  • n
  • .
  • j
  • s
  • o
  • n
  • `
  • ,
  • a
  • n
  • d
  • d
  • e
  • p
  • l
  • o
  • y
  • e
  • d
  • w
  • e
  • e
  • k
  • l
  • y
  • s
  • y
  • s
  • t
  • e
  • m
  • d
  • t
  • i
  • m
  • e
  • r
  • s
  • t
  • h
  • a
  • t
  • p
  • r
  • u
  • n
  • e
  • d
  • a
  • n
  • g
  • l
  • i
  • n
  • g
  • i
  • m
  • a
  • g
  • e
  • s
  • o
  • l
  • d
  • e
  • r
  • t
  • h
  • a
  • n
  • 7
  • d
  • a
  • y
  • s
  • u
  • s
  • i
  • n
  • g
  • t
  • h
  • e
  • `
  • u
  • n
  • t
  • i
  • l
  • `
  • f
  • i
  • l
  • t
  • e
  • r
  • .
⛔ 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 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 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 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 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 →