Unable to access Docker Host in Linux VM from Windows host











up vote
0
down vote

favorite












I'm performing some work for a client and wish to create Docker containers to scale my test automation environments in order to reduce my feedback loop.



I'm using the below set-up:





  • O/S: Windows 7


  • Interface: Oracle VirtualBox 5.2.8


  • Docker Version: 18.03.0-ce


  • Network: On client network, so no access to Docker Hub or the like as restricted. Using Boot2Docker ISO to run Docker Quickstart Terminal


When i run Docker Quickstart Terminal i get the below meesage during set-up:




This machine has been allocated an IP address, but Docker Machine
could not reach it successfully. SSH for the machine should still
work, but connecting to exposed ports, such as the Docker daemon port
(usually :2376), may not work properly.




It then goes on to say




Error checking TLS connection: Error checking and/or regenerating the
certs: There was an error validating certificates for host
"192.168.99.100:2376":




While i can play with Docker, and build images/run containers, i really need my Jenkins instance, which sits on the windows host, to be able to access the Docker host so it can spin up containers as and when needed (See [https://wiki.jenkins.io/display/JENKINS/Docker+Plugin).



I have scoured the internet, and tried numerous fixes. One included changing the port to 2375 - However, i have since learned this is an unsecure port and as such, not suitable for my client.



I am a bit restricted in what i can do due to my O/S and the lack of access to Docker Hub/Github. While i can't change my O/S, it's might be a possibility to get a later version of the Docker Toolbox if needed.



My windows host can ping the Docker Host IP no problems, it just can't access that port. I have checked the certs on both my machine and within the Docker Host (within the Boot2Docker folder) and they both match exactly.



The only thing i can think is that my client has some security around this particular port or the connection i am trying to make.



Just to note, i am very new to Docker, so it's possible that my understanding is incorrect. Also, this is all on my laptop, because i always build everything locally to make sure it works before deploying to any servers etc.



I also have access to Git Bash which i have used to run various docker-machine commands, albeit to no luck.



Can anyone suggest a fix for this? Or provide any advice on how i can circumvent this issue?










share|improve this question




























    up vote
    0
    down vote

    favorite












    I'm performing some work for a client and wish to create Docker containers to scale my test automation environments in order to reduce my feedback loop.



    I'm using the below set-up:





    • O/S: Windows 7


    • Interface: Oracle VirtualBox 5.2.8


    • Docker Version: 18.03.0-ce


    • Network: On client network, so no access to Docker Hub or the like as restricted. Using Boot2Docker ISO to run Docker Quickstart Terminal


    When i run Docker Quickstart Terminal i get the below meesage during set-up:




    This machine has been allocated an IP address, but Docker Machine
    could not reach it successfully. SSH for the machine should still
    work, but connecting to exposed ports, such as the Docker daemon port
    (usually :2376), may not work properly.




    It then goes on to say




    Error checking TLS connection: Error checking and/or regenerating the
    certs: There was an error validating certificates for host
    "192.168.99.100:2376":




    While i can play with Docker, and build images/run containers, i really need my Jenkins instance, which sits on the windows host, to be able to access the Docker host so it can spin up containers as and when needed (See [https://wiki.jenkins.io/display/JENKINS/Docker+Plugin).



    I have scoured the internet, and tried numerous fixes. One included changing the port to 2375 - However, i have since learned this is an unsecure port and as such, not suitable for my client.



    I am a bit restricted in what i can do due to my O/S and the lack of access to Docker Hub/Github. While i can't change my O/S, it's might be a possibility to get a later version of the Docker Toolbox if needed.



    My windows host can ping the Docker Host IP no problems, it just can't access that port. I have checked the certs on both my machine and within the Docker Host (within the Boot2Docker folder) and they both match exactly.



    The only thing i can think is that my client has some security around this particular port or the connection i am trying to make.



    Just to note, i am very new to Docker, so it's possible that my understanding is incorrect. Also, this is all on my laptop, because i always build everything locally to make sure it works before deploying to any servers etc.



    I also have access to Git Bash which i have used to run various docker-machine commands, albeit to no luck.



    Can anyone suggest a fix for this? Or provide any advice on how i can circumvent this issue?










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm performing some work for a client and wish to create Docker containers to scale my test automation environments in order to reduce my feedback loop.



      I'm using the below set-up:





      • O/S: Windows 7


      • Interface: Oracle VirtualBox 5.2.8


      • Docker Version: 18.03.0-ce


      • Network: On client network, so no access to Docker Hub or the like as restricted. Using Boot2Docker ISO to run Docker Quickstart Terminal


      When i run Docker Quickstart Terminal i get the below meesage during set-up:




      This machine has been allocated an IP address, but Docker Machine
      could not reach it successfully. SSH for the machine should still
      work, but connecting to exposed ports, such as the Docker daemon port
      (usually :2376), may not work properly.




      It then goes on to say




      Error checking TLS connection: Error checking and/or regenerating the
      certs: There was an error validating certificates for host
      "192.168.99.100:2376":




      While i can play with Docker, and build images/run containers, i really need my Jenkins instance, which sits on the windows host, to be able to access the Docker host so it can spin up containers as and when needed (See [https://wiki.jenkins.io/display/JENKINS/Docker+Plugin).



      I have scoured the internet, and tried numerous fixes. One included changing the port to 2375 - However, i have since learned this is an unsecure port and as such, not suitable for my client.



      I am a bit restricted in what i can do due to my O/S and the lack of access to Docker Hub/Github. While i can't change my O/S, it's might be a possibility to get a later version of the Docker Toolbox if needed.



      My windows host can ping the Docker Host IP no problems, it just can't access that port. I have checked the certs on both my machine and within the Docker Host (within the Boot2Docker folder) and they both match exactly.



      The only thing i can think is that my client has some security around this particular port or the connection i am trying to make.



      Just to note, i am very new to Docker, so it's possible that my understanding is incorrect. Also, this is all on my laptop, because i always build everything locally to make sure it works before deploying to any servers etc.



      I also have access to Git Bash which i have used to run various docker-machine commands, albeit to no luck.



      Can anyone suggest a fix for this? Or provide any advice on how i can circumvent this issue?










      share|improve this question















      I'm performing some work for a client and wish to create Docker containers to scale my test automation environments in order to reduce my feedback loop.



      I'm using the below set-up:





      • O/S: Windows 7


      • Interface: Oracle VirtualBox 5.2.8


      • Docker Version: 18.03.0-ce


      • Network: On client network, so no access to Docker Hub or the like as restricted. Using Boot2Docker ISO to run Docker Quickstart Terminal


      When i run Docker Quickstart Terminal i get the below meesage during set-up:




      This machine has been allocated an IP address, but Docker Machine
      could not reach it successfully. SSH for the machine should still
      work, but connecting to exposed ports, such as the Docker daemon port
      (usually :2376), may not work properly.




      It then goes on to say




      Error checking TLS connection: Error checking and/or regenerating the
      certs: There was an error validating certificates for host
      "192.168.99.100:2376":




      While i can play with Docker, and build images/run containers, i really need my Jenkins instance, which sits on the windows host, to be able to access the Docker host so it can spin up containers as and when needed (See [https://wiki.jenkins.io/display/JENKINS/Docker+Plugin).



      I have scoured the internet, and tried numerous fixes. One included changing the port to 2375 - However, i have since learned this is an unsecure port and as such, not suitable for my client.



      I am a bit restricted in what i can do due to my O/S and the lack of access to Docker Hub/Github. While i can't change my O/S, it's might be a possibility to get a later version of the Docker Toolbox if needed.



      My windows host can ping the Docker Host IP no problems, it just can't access that port. I have checked the certs on both my machine and within the Docker Host (within the Boot2Docker folder) and they both match exactly.



      The only thing i can think is that my client has some security around this particular port or the connection i am trying to make.



      Just to note, i am very new to Docker, so it's possible that my understanding is incorrect. Also, this is all on my laptop, because i always build everything locally to make sure it works before deploying to any servers etc.



      I also have access to Git Bash which i have used to run various docker-machine commands, albeit to no luck.



      Can anyone suggest a fix for this? Or provide any advice on how i can circumvent this issue?







      linux docker jenkins virtualbox boot2docker






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 9 at 23:31

























      asked Nov 9 at 23:25









      Rusty Shackleford

      929




      929





























          active

          oldest

          votes











          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%2f53234516%2funable-to-access-docker-host-in-linux-vm-from-windows-host%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2f53234516%2funable-to-access-docker-host-in-linux-vm-from-windows-host%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

          Landwehr

          Reims

          Javascript gets undefined on array