advancedTop 100 Interview Questions
What happens to an anonymous volume created implicitly by a Dockerfile's VOLUME instruction if you don't bind it explicitly?
Docker still creates an anonymous, randomly-named volume to satisfy the mount point, but because it has no memorable name or reference, it's easy to accumulate orphaned anonymous volumes over time unless explicitly cleaned up with `docker volume prune`.
This is a Pro chapter
Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.
What happens to an anonymous volume created implicitly by a Dockerfile's VOLUME instruction if you don't bind it explicitly?