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

  • Appoxo@lemmy.dbzer0.comEnglish
    11·
    17 days ago

    Literally 90% of my vompose looks like this.
    But it mskes it easier with permissions as the mainrainer doesnt have to provide any infornation to noobs like me.