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