6 ms·
AFAIK volumes are nothing more than a bind mount on a private docker folder, e.g. the files for volume my-volume are stored in /var/lib/docker/volumes/my-volume
by mrighele 4mo ago
AFAIK volumes are nothing more than a bind mount on a private docker folder, e.g. the files for volume my-volume are stored in /var/lib/docker/volumes/my-volume/_data, so backup strategies (an problems) for bind mounts apply also to volumes
- c0balt 4mo agoYep, that is accurate. There is also a command/API route to find the path on disk iirc. In my setups it just was easier to use fixed paths (or relative to project dir) from a permissions management perspective. Backup tools did not always have to/should run as root which is helpful on machines providing multiple distinct services. Putting borg or a similar tool in a container that is part of the compose manifest file can also help. I haven't seen this used in practice though yet.