是否支持不依赖tmpfs的Docker临时卷？大写入量场景技术问询

Great question—this is a super common pain point when dealing with high-write workloads in Docker, especially when you can’t rely on tmpfs due to memory constraints. Let’s break down the viable solutions that avoid both Docker’s storage driver (which Docker explicitly discourages for heavy writes) and tmpfs:

1. Bind Mounts to Host Disk-Based Temporary Directories #

Instead of using tmpfs (which ties to host memory), you can mount a disk-based temporary directory from the host into your container. This bypasses Docker’s layered storage driver entirely, uses physical disk space, and doesn’t consume host memory beyond what the application itself uses.

How to implement: #

• First, create a dedicated temporary directory on your host (or use an existing one like /var/tmp, which is persisted longer than /tmp in most Linux distros):

  mkdir -p /host/temp/app-writes
  

• Then mount it into your container:

  docker run -v /host/temp/app-writes:/path/in/container your-app-image
  

• Bonus: You can automate cleanup of this directory using tools like tmpfiles.d (on systemd-based hosts) to avoid disk bloat over time.

2. Anonymous or Named Docker Volumes (Local Driver) #

Docker’s default local volume driver stores data on the host’s disk (in /var/lib/docker/volumes/), completely separate from the container’s writable layer. This is Docker’s recommended alternative to both storage driver writes and tmpfs for disk-backed temporary storage.

Two variations: #

• Anonymous Volumes (Auto-Cleaned): Use this if you want the volume to be deleted automatically when the container is removed. Add -v /path/in/container (no host path specified) and the --rm flag:

  docker run --rm -v /path/in/container your-app-image
  

• Named Volumes (Manual Cleanup): Create a named volume for explicit control, then delete it when you’re done:

  # Create the volume
  docker volume create temp-app-volume
  # Run the container with the volume mounted
  docker run -v temp-app-volume:/path/in/container your-app-image
  # Cleanup when finished
  docker volume rm temp-app-volume
  

3. Ephemeral Volumes with Custom Local Configurations #

If you need more control (like setting specific disk quotas or filesystem types), you can configure the local volume driver with additional options. For example, you can mount a dedicated disk partition or a filesystem with compression for temporary writes:

docker volume create --driver local \
  --opt type=ext4 \
  --opt device=/dev/sdb1 \
  --opt o=rw,noatime \
  temp-high-write-volume

Key Notes to Remember: #

• All these solutions avoid Docker’s storage driver writable layers, so you won’t hit the performance or disk bloat issues Docker warns about.
• Unlike tmpfs, they use physical disk space, so you don’t have to worry about exceeding host memory or impacting other memory-heavy processes.
• Always monitor disk usage on the host to ensure temporary writes don’t fill up the filesystem.

内容的提问来源于stack exchange，提问作者andresp