Bird
0
0

After executing docker system prune --volumes, volumes were not deleted. What is the most probable reason?

medium📝 Troubleshoot Q6 of 15
Docker - Resource Management
After executing docker system prune --volumes, volumes were not deleted. What is the most probable reason?
AThe volumes are still in use by at least one container
BThe <code>--volumes</code> flag is deprecated and ignored
CDocker daemon needs to be restarted to apply prune changes
DThe command requires <code>-a</code> flag to remove volumes
Step-by-Step Solution
Solution:

  1. Step 1: Understand volume removal conditions

    Docker only removes unused volumes; volumes attached to containers are preserved.

  2. Step 2: Check volume usage

    If volumes are still referenced by containers, prune will not delete them even with --volumes.

  3. Final Answer:

    The volumes are still in use by at least one container -> Option A

  4. Quick Check:

    Volumes in use are never removed [OK]
Quick Trick: Volumes must be unused to be pruned with --volumes [OK]
Common Mistakes:
  • Assuming --volumes removes all volumes regardless of usage
  • Believing daemon restart is needed
  • Thinking -a flag is required for volumes

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Docker Quizzes
Docker Security - Read-only filesystem containers - Quiz 13medium Docker Security - Scanning images for vulnerabilities - Quiz 11easy Docker Swarm - Swarm mode initialization - Quiz 4medium Docker in CI/CD - Docker layer caching in CI - Quiz 10hard Docker in CI/CD - GitHub Actions with Docker - Quiz 11easy Production Patterns - Sidecar container pattern - Quiz 14medium Production Patterns - Canary deployment pattern - Quiz 10hard Production Patterns - Blue-green deployment with containers - Quiz 3easy Production Patterns - Ambassador container pattern - Quiz 13medium Resource Management - Container disk usage management - Quiz 11easy