Hei there. I’ve read that it’s best practice to use docker volumes to store persistent container data (such as config, files) instead of using bindmount. So far, I’ve only used the latter and would like to change this.

From what I’ve read, all volumes are stored in var/lib/docker/volumes. I also understood, that a volume is basically a subdirectory in that path.

I’d like to keep things organized and would like the volumes of my containers to be stored in subdirectories for each stack in docker compose, e.g.

volumes/arr/qbit /arr/gluetun /nextcloud/nextcloud /nextcloud/database

Is this possible using compose?

Another noob question: is there any disadvantage to using the default network docker creates for each stack/container?

  • TheHolm@aussie.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    9 months ago

    Do not access volumes directly on filesystem. path may change. If you need access data on a volume just spawn temporary container an mount that volume.