Why Docker mounts only specific files in volume?











up vote
-3
down vote

favorite












$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.13.6
BuildVersion: 17G65

$ docker -v
Docker version 18.06.0-ce, build 0ffa825


I have some docker-compose file that actually has this string of line:



volumes:
- .:/sql


And In "." directory I have plenty of directories and files:



$ ls -l
total 32
-rw-r--r-- 1 michael staff 161 Nov 9 13:35 README.ms
drwxr-xr-x 12 michael staff 384 Nov 9 13:35 backend
-rwxr-xr-x 1 michael staff 1438 Nov 9 13:35 manage.py
drwxr-xr-x 12 michael staff 384 Nov 10 13:28 ops
drwxr-xr-x 5 michael staff 160 Nov 9 13:35 requirements
-rw-r--r-- 1 michael staff 38 Nov 9 13:35 requirements.txt


But when I start this container and go inside, all I see there:



# ls -1 /sql
docker-compose.yml
ops


Pay attention: file docker-compose.yml is even not from this directory. It is from ops/



Who has an idea of the cause?










share|improve this question


























    up vote
    -3
    down vote

    favorite












    $ sw_vers
    ProductName: Mac OS X
    ProductVersion: 10.13.6
    BuildVersion: 17G65

    $ docker -v
    Docker version 18.06.0-ce, build 0ffa825


    I have some docker-compose file that actually has this string of line:



    volumes:
    - .:/sql


    And In "." directory I have plenty of directories and files:



    $ ls -l
    total 32
    -rw-r--r-- 1 michael staff 161 Nov 9 13:35 README.ms
    drwxr-xr-x 12 michael staff 384 Nov 9 13:35 backend
    -rwxr-xr-x 1 michael staff 1438 Nov 9 13:35 manage.py
    drwxr-xr-x 12 michael staff 384 Nov 10 13:28 ops
    drwxr-xr-x 5 michael staff 160 Nov 9 13:35 requirements
    -rw-r--r-- 1 michael staff 38 Nov 9 13:35 requirements.txt


    But when I start this container and go inside, all I see there:



    # ls -1 /sql
    docker-compose.yml
    ops


    Pay attention: file docker-compose.yml is even not from this directory. It is from ops/



    Who has an idea of the cause?










    share|improve this question
























      up vote
      -3
      down vote

      favorite









      up vote
      -3
      down vote

      favorite











      $ sw_vers
      ProductName: Mac OS X
      ProductVersion: 10.13.6
      BuildVersion: 17G65

      $ docker -v
      Docker version 18.06.0-ce, build 0ffa825


      I have some docker-compose file that actually has this string of line:



      volumes:
      - .:/sql


      And In "." directory I have plenty of directories and files:



      $ ls -l
      total 32
      -rw-r--r-- 1 michael staff 161 Nov 9 13:35 README.ms
      drwxr-xr-x 12 michael staff 384 Nov 9 13:35 backend
      -rwxr-xr-x 1 michael staff 1438 Nov 9 13:35 manage.py
      drwxr-xr-x 12 michael staff 384 Nov 10 13:28 ops
      drwxr-xr-x 5 michael staff 160 Nov 9 13:35 requirements
      -rw-r--r-- 1 michael staff 38 Nov 9 13:35 requirements.txt


      But when I start this container and go inside, all I see there:



      # ls -1 /sql
      docker-compose.yml
      ops


      Pay attention: file docker-compose.yml is even not from this directory. It is from ops/



      Who has an idea of the cause?










      share|improve this question













      $ sw_vers
      ProductName: Mac OS X
      ProductVersion: 10.13.6
      BuildVersion: 17G65

      $ docker -v
      Docker version 18.06.0-ce, build 0ffa825


      I have some docker-compose file that actually has this string of line:



      volumes:
      - .:/sql


      And In "." directory I have plenty of directories and files:



      $ ls -l
      total 32
      -rw-r--r-- 1 michael staff 161 Nov 9 13:35 README.ms
      drwxr-xr-x 12 michael staff 384 Nov 9 13:35 backend
      -rwxr-xr-x 1 michael staff 1438 Nov 9 13:35 manage.py
      drwxr-xr-x 12 michael staff 384 Nov 10 13:28 ops
      drwxr-xr-x 5 michael staff 160 Nov 9 13:35 requirements
      -rw-r--r-- 1 michael staff 38 Nov 9 13:35 requirements.txt


      But when I start this container and go inside, all I see there:



      # ls -1 /sql
      docker-compose.yml
      ops


      Pay attention: file docker-compose.yml is even not from this directory. It is from ops/



      Who has an idea of the cause?







      docker docker-compose docker-volume






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 10 at 12:27









      Michael A.

      9717




      9717
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          Figured out the reason.



          No matter where you start docker-compose from, it takes "." as a location of docker-compose.yml file. Thus, all you expect to see inside container have to be located within the very same directory where docker-compose.yml resides at.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53238949%2fwhy-docker-mounts-only-specific-files-in-volume%23new-answer', 'question_page');
            }
            );

            Post as a guest
































            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            Figured out the reason.



            No matter where you start docker-compose from, it takes "." as a location of docker-compose.yml file. Thus, all you expect to see inside container have to be located within the very same directory where docker-compose.yml resides at.






            share|improve this answer

























              up vote
              0
              down vote













              Figured out the reason.



              No matter where you start docker-compose from, it takes "." as a location of docker-compose.yml file. Thus, all you expect to see inside container have to be located within the very same directory where docker-compose.yml resides at.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                Figured out the reason.



                No matter where you start docker-compose from, it takes "." as a location of docker-compose.yml file. Thus, all you expect to see inside container have to be located within the very same directory where docker-compose.yml resides at.






                share|improve this answer












                Figured out the reason.



                No matter where you start docker-compose from, it takes "." as a location of docker-compose.yml file. Thus, all you expect to see inside container have to be located within the very same directory where docker-compose.yml resides at.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 10 at 12:32









                Michael A.

                9717




                9717






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53238949%2fwhy-docker-mounts-only-specific-files-in-volume%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest




















































































                    Popular posts from this blog

                    Florida Star v. B. J. F.

                    Error while running script in elastic search , gateway timeout

                    Adding quotations to stringified JSON object values