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?

  • Matt The Horwood@lemmy.horwood.cloud
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    If you have data else where on your server, you can use the options to volume to direct the mount there

    driver: local driver_opts: type: none o: bind device: ‘/your/current/data’

    Also reading the compose spec will help

    • Pete90@feddit.deOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Thanks, this looks like it’ll do the job. I have not a lot of knowledge, so the specs are often a bit technical for me. I’ll give it a go, thanks!

      • ErwinLottemann@feddit.de
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        that is using bin mounts again. and i don’t get why this is discouraged, i actualy do like to know where my data is stored and don’t want to spin up a container that backs up using the volumes managed by docker. at that point you are using bind mounts again anyway.

        regarding your original question, i don’t think it is possible (or even useful) to tell docker where to store the volumes for each compose stack because you are not supposed to access the from the filesystem directly anyway.

        just continue using bind mounts