Explain why we use named volumes, link to Docker's explanation about named volumes vs bind mounts #613

New Issue

3wordchant · 2024-04-26T01:15:03Z

3wordchant commented

2024-04-26 01:15:03 +00:00

(Thanks to Sutty.nl for the questions and research which led to this report, apologies for my probably-dubious translation from Spanish)

Many folks using Docker are probably used to using bind mounts; these are recommended in many (most?) upstream docker-compose files, and at one point Docker recommended bind mounts over named mounts due to poor performance of the Linux named volume storage drivers.

Currently, Co-op Cloud exclusively uses named volumes (except for rare special-case bind mounts, like Traefik and Caddy getting access to the host's /var/run/docker.sock).

It could be useful to link to Docker's "Good use cases for volumes" page, and/or the "Use volumes for write-heavy workload" docs to help explain why we recommend named volumes, and what potential trade-offs there are.

(Thanks to Sutty.nl for the questions and research which led to this report, apologies for my probably-dubious translation from Spanish) Many folks using Docker are probably used to using bind mounts; these are recommended in many (most?) upstream docker-compose files, and at one point Docker recommended bind mounts over named mounts due to poor performance of the Linux named volume storage drivers. Currently, Co-op Cloud exclusively uses named volumes (except for rare special-case bind mounts, like Traefik and Caddy getting access to the host's `/var/run/docker.sock`). It could be useful to link to Docker's ["Good use cases for volumes"](https://docs.docker.com/storage/#good-use-cases-for-volumes) page, and/or the ["Use volumes for write-heavy workload"](https://docs.docker.com/storage/storagedriver/overlayfs-driver/#use-volumes-for-write-heavy-workloads) docs to help explain why we recommend named volumes, and what potential trade-offs there are.

🎉 1

3wordchant added the

enhancement

documentation

labels 2024-04-26 01:15:03 +00:00

Sign in to join this conversation.