All docker files look something like this

services:
  service_name:
    image: author/project:latest
    container_name: service_name
    volumes:
      - service_data:/app/data/

volumes:
  service_data:

Yes, this makes the data to persist, but it creates a directory with a random name inside /var/lib/docker/volumes/
This makes it really hard to actually have ownership of the data of the service (for example to create backups, or to migrate to another host)

Why is it standard practice to use this instead of having a directory mounted inside at the same level you have your docker-compose.yml?
Like this - ./service_data:/app/data

  • StrawberryPigtails@lemmy.sdf.orgEnglish
    10·
    3 days ago

    I tend to change volumes to bind mounts. Makes it easier to backup or move the service.

    Might want to avoid using relative paths with bind mounts and declare the full path. It has caused me headaches before.