![\"docker-compose\"](\"http:\/\/www.scmgalaxy.com\/tutorials\/wp-content\/uploads\/2018\/01\/docker-compose.png\")
<\/p>\n<\/p>\n
Issues – docker-compose prepends current directory name to named volumes<\/p>\n
What actually happens is that the named volume gets prepended with (a simplified version of) the directory name from which the docker-compose command was run.<\/p>\n
For instance, if I run from the “dcompos-programs” directory, and I name the volume “my_named_vol”, then I end up with a volume named “dcompos-programs_my_named_vol”.<\/p>\n
docker-compose-named-volume.yml:<\/strong><\/p>\n [text]<\/p>\n version: ‘3’ solr: [\/text]<\/p>\n Result:<\/strong><\/p>\n [text]<\/p>\n $ docker-compose -f docker-compose-named-volume.yml up -d && \\ [\/text]<\/p>\n Answer<\/strong> Docker Tutorials Fundamental To Advanced-2021 Crash Course:- https:\/\/bit.ly\/3hOIbTB<\/a><\/p>\n You can use the external volume setting to avoid the prefix.
\nservices:<\/p>\n
\nimage: alpine:3.5
\ncontainer_name: foo
\nvolumes:
\n– my_named_vol:\/opt\/foo
\nvolumes:
\nmy_named_vol:<\/p>\n
\n> echo “## named volume:” && \\
\n> docker volume ls | grep my_named_vol && \\
\n> echo “## stop” && \\
\n> docker-compose -f docker-compose-named-volume.yml down && \\
\n> echo “## rm volume” && \\
\n> docker volume rm $(docker volume ls | grep my_named_vol | awk ‘{print $2}’)
\nCreating network “deploymentroot_default” with the default driver
\nCreating volume “dcompos-programs_my_named_vol” with default driver
\nCreating foo<\/p>\n
\ndocker-compose uses a project name. By default it\u2019s the directory name which prevents collisions with existing containers. But you can use -p to change the prefix name.<\/p>\n
\nhttps:\/\/docs.docker.com\/compose\/compose-file\/#external<\/a><\/p>\n\n