Volume Mounts

  • persistent storage mechanisms managed by the Docker daemon
  • retain data even after containers using them are removed
  • volume data is stored on the filesystem on the host
  • only accessible from within container, not from host

Bind Mounts

  • create a direct link between a host system path and a container
  • accessible from both container and host

tmpfs Mounts

  • stores files directly in the host’s primary memory (not written to disk)
  • storage is non-persistent
  • used for caching, handling sensitive information, or reducing disk I/O

Named Pipes

  • used for communication between the Docker host and a container
  • common use case is to run a third-party tool inside of a container and connect to the Docker Engine API using a named pipe