Eliminating the impact of UnionFS on results when benchmarking inside Docker Eliminating the impact of UnionFS on results when benchmarking inside Docker linux linux

Eliminating the impact of UnionFS on results when benchmarking inside Docker


As mentioned in "Mount a shared-storage volume as a data volume"

In addition to mounting a host directory in your container, some Docker volume plugins allow you to provision and mount shared storage, such as iSCSI, NFS, or FC.

Since docker 1.9, this is done with docker volume create (and then you mount those volumes in their expected paths in the container)

That allows you to:

Which directories in the Docker container should be mounted from host

Any folder which include persistent data, and/or has an high volume of IO operations.