Run with volume for files generated during docker build





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I am using Docker to run unit tests, to generate Cobertura code coverage results, and then to generate an HTML reports on this (using ReportGenerator). I then publish BOTH the code coverage results file and the HTML reports to VSTS DevOps.



Here are the commands I need to run:



# Generates coverage.cobertura.xml for use in the next step.
dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=codecoveragereports/

# Generates HTML reports from coverage.cobertura.xml file.
dotnet reportgenerator -reports:app/test/MyApplication.UnitTests/codecoveragereports/coverage.cobertura.xml -targetdir:codecoveragereports -reportTypes:htmlInline


And now in dockerfile:



WORKDIR ./app/test/MyApplication.UnitTests/

RUN dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=codecoveragereports/

ENTRYPOINT ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]


And to build the image:



docker build -t myapplication.tests -f dockerfile --target tester .


And to run it:



docker run --rm -it -v $PWD/codecoveragereports:/app/test/MyApplication.UnitTests/codecoveragereports myapplication.tests:latest


The problem:



The results file generated on dotnet test does get generated (I can test this with RUN dir), but seems to disappear when I specify a volume (using -v) on docker run.



Is it not possible to create a volume on files which are generated in the image during docker build?










share|improve this question





























    0















    I am using Docker to run unit tests, to generate Cobertura code coverage results, and then to generate an HTML reports on this (using ReportGenerator). I then publish BOTH the code coverage results file and the HTML reports to VSTS DevOps.



    Here are the commands I need to run:



    # Generates coverage.cobertura.xml for use in the next step.
    dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=codecoveragereports/

    # Generates HTML reports from coverage.cobertura.xml file.
    dotnet reportgenerator -reports:app/test/MyApplication.UnitTests/codecoveragereports/coverage.cobertura.xml -targetdir:codecoveragereports -reportTypes:htmlInline


    And now in dockerfile:



    WORKDIR ./app/test/MyApplication.UnitTests/

    RUN dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=codecoveragereports/

    ENTRYPOINT ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]


    And to build the image:



    docker build -t myapplication.tests -f dockerfile --target tester .


    And to run it:



    docker run --rm -it -v $PWD/codecoveragereports:/app/test/MyApplication.UnitTests/codecoveragereports myapplication.tests:latest


    The problem:



    The results file generated on dotnet test does get generated (I can test this with RUN dir), but seems to disappear when I specify a volume (using -v) on docker run.



    Is it not possible to create a volume on files which are generated in the image during docker build?










    share|improve this question

























      0












      0








      0


      0






      I am using Docker to run unit tests, to generate Cobertura code coverage results, and then to generate an HTML reports on this (using ReportGenerator). I then publish BOTH the code coverage results file and the HTML reports to VSTS DevOps.



      Here are the commands I need to run:



      # Generates coverage.cobertura.xml for use in the next step.
      dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=codecoveragereports/

      # Generates HTML reports from coverage.cobertura.xml file.
      dotnet reportgenerator -reports:app/test/MyApplication.UnitTests/codecoveragereports/coverage.cobertura.xml -targetdir:codecoveragereports -reportTypes:htmlInline


      And now in dockerfile:



      WORKDIR ./app/test/MyApplication.UnitTests/

      RUN dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=codecoveragereports/

      ENTRYPOINT ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]


      And to build the image:



      docker build -t myapplication.tests -f dockerfile --target tester .


      And to run it:



      docker run --rm -it -v $PWD/codecoveragereports:/app/test/MyApplication.UnitTests/codecoveragereports myapplication.tests:latest


      The problem:



      The results file generated on dotnet test does get generated (I can test this with RUN dir), but seems to disappear when I specify a volume (using -v) on docker run.



      Is it not possible to create a volume on files which are generated in the image during docker build?










      share|improve this question














      I am using Docker to run unit tests, to generate Cobertura code coverage results, and then to generate an HTML reports on this (using ReportGenerator). I then publish BOTH the code coverage results file and the HTML reports to VSTS DevOps.



      Here are the commands I need to run:



      # Generates coverage.cobertura.xml for use in the next step.
      dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=codecoveragereports/

      # Generates HTML reports from coverage.cobertura.xml file.
      dotnet reportgenerator -reports:app/test/MyApplication.UnitTests/codecoveragereports/coverage.cobertura.xml -targetdir:codecoveragereports -reportTypes:htmlInline


      And now in dockerfile:



      WORKDIR ./app/test/MyApplication.UnitTests/

      RUN dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=codecoveragereports/

      ENTRYPOINT ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]


      And to build the image:



      docker build -t myapplication.tests -f dockerfile --target tester .


      And to run it:



      docker run --rm -it -v $PWD/codecoveragereports:/app/test/MyApplication.UnitTests/codecoveragereports myapplication.tests:latest


      The problem:



      The results file generated on dotnet test does get generated (I can test this with RUN dir), but seems to disappear when I specify a volume (using -v) on docker run.



      Is it not possible to create a volume on files which are generated in the image during docker build?







      docker dockerfile






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 26 '18 at 14:32









      Dave NewDave New

      16.3k33138305




      16.3k33138305
























          1 Answer
          1






          active

          oldest

          votes


















          1














          The life of your container can be very roughly represented like



          docker build




          • dot test --> codecoveragereports/


          docker run -v




          1. docker mount volume $PWD/codecoveragereports to codecoveragereports, this obscured the previous codecoveragereports

          2. your entrypoint script


          So you need to output dot test to a temp folder, then copy it to your mount point at runtime (in the entrypoint).



          dockerfile



          COPY init.sh /
          dot test --> /temp/
          ENTRYPOINT ['/bin/bash', '/init.sh']


          init.sh



          cp /temp /app/test/MyApplication.UnitTests/codecoveragereports
          exec ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]





          share|improve this answer
























          • @davenewza why do you want to copy to a temp folder?

            – Siyu
            Nov 26 '18 at 17:58












          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',
          autoActivateHeartbeat: false,
          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%2f53483327%2frun-with-volume-for-files-generated-during-docker-build%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          The life of your container can be very roughly represented like



          docker build




          • dot test --> codecoveragereports/


          docker run -v




          1. docker mount volume $PWD/codecoveragereports to codecoveragereports, this obscured the previous codecoveragereports

          2. your entrypoint script


          So you need to output dot test to a temp folder, then copy it to your mount point at runtime (in the entrypoint).



          dockerfile



          COPY init.sh /
          dot test --> /temp/
          ENTRYPOINT ['/bin/bash', '/init.sh']


          init.sh



          cp /temp /app/test/MyApplication.UnitTests/codecoveragereports
          exec ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]





          share|improve this answer
























          • @davenewza why do you want to copy to a temp folder?

            – Siyu
            Nov 26 '18 at 17:58
















          1














          The life of your container can be very roughly represented like



          docker build




          • dot test --> codecoveragereports/


          docker run -v




          1. docker mount volume $PWD/codecoveragereports to codecoveragereports, this obscured the previous codecoveragereports

          2. your entrypoint script


          So you need to output dot test to a temp folder, then copy it to your mount point at runtime (in the entrypoint).



          dockerfile



          COPY init.sh /
          dot test --> /temp/
          ENTRYPOINT ['/bin/bash', '/init.sh']


          init.sh



          cp /temp /app/test/MyApplication.UnitTests/codecoveragereports
          exec ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]





          share|improve this answer
























          • @davenewza why do you want to copy to a temp folder?

            – Siyu
            Nov 26 '18 at 17:58














          1












          1








          1







          The life of your container can be very roughly represented like



          docker build




          • dot test --> codecoveragereports/


          docker run -v




          1. docker mount volume $PWD/codecoveragereports to codecoveragereports, this obscured the previous codecoveragereports

          2. your entrypoint script


          So you need to output dot test to a temp folder, then copy it to your mount point at runtime (in the entrypoint).



          dockerfile



          COPY init.sh /
          dot test --> /temp/
          ENTRYPOINT ['/bin/bash', '/init.sh']


          init.sh



          cp /temp /app/test/MyApplication.UnitTests/codecoveragereports
          exec ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]





          share|improve this answer













          The life of your container can be very roughly represented like



          docker build




          • dot test --> codecoveragereports/


          docker run -v




          1. docker mount volume $PWD/codecoveragereports to codecoveragereports, this obscured the previous codecoveragereports

          2. your entrypoint script


          So you need to output dot test to a temp folder, then copy it to your mount point at runtime (in the entrypoint).



          dockerfile



          COPY init.sh /
          dot test --> /temp/
          ENTRYPOINT ['/bin/bash', '/init.sh']


          init.sh



          cp /temp /app/test/MyApplication.UnitTests/codecoveragereports
          exec ["/bin/bash", "-c", "dotnet reportgenerator -reports:codecoveragereports/*.xml -targetdir:codecoveragereports -reportTypes:htmlInline"]






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 26 '18 at 16:21









          SiyuSiyu

          3,22211231




          3,22211231













          • @davenewza why do you want to copy to a temp folder?

            – Siyu
            Nov 26 '18 at 17:58



















          • @davenewza why do you want to copy to a temp folder?

            – Siyu
            Nov 26 '18 at 17:58

















          @davenewza why do you want to copy to a temp folder?

          – Siyu
          Nov 26 '18 at 17:58





          @davenewza why do you want to copy to a temp folder?

          – Siyu
          Nov 26 '18 at 17:58




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53483327%2frun-with-volume-for-files-generated-during-docker-build%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Wiesbaden

          Marschland

          Dieringhausen