Docker consul cluster without swarm












0















Due to company restrictions I cannot use docker-swarm, so I am trying to setup a consul cluster on multiple machines sharing the same host network, let's pretend these are the 3 machines addresses (I am using virtualbox with docker-machine for testing), these IP are known as HOST_IP by their containers:





  • dm1: 192.168.99.100


  • dm2: 192.168.99.101


  • dm3: 192.168.99.102


CONSUL_BOOTSTRAP_IP is the main consul bootstrap server 192.168.99.100.



This setup works (I get the 3 nodes up and running in the web UI) but I get some weird logs in the containers:



consul-server_1_46f1167db7a9 |     2018/11/14 08:06:48 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host

consul-server_1_46f1167db7a9 |     2018/11/14 08:06:50 [WARN] consul: error getting server health from "64bbf570ff39": context deadline exceeded

consul-server_1_46f1167db7a9 |     2018/11/14 08:06:51 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host

consul-server_1_46f1167db7a9 |     2018/11/14 08:06:52 [WARN] consul: error getting server health from "64bbf570ff39": context deadline exceeded

consul-server_1_46f1167db7a9 |     2018/11/14 08:06:53 [WARN] consul: error getting server health from "64bbf570ff39": last request still outstanding

consul-server_1_46f1167db7a9 |     2018/11/14 08:06:54 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host


Why is consul trying to access the docker container internal IP 172.18.0.* instead of using the -advertise address ? This is annoying and in the UI I can see some ghost nodes appearing and disappearing with an error status.



Here are my compose files:



dm1



version: '2'



services:

    consul-server:

        image: consul:latest

        networks:

            - back

        command:

            agent

            -node consul-01

            -server

            -client 0.0.0.0

            -bootstrap-expect 3

            -ui

            -advertise ${HOST_IP}

        ports:

            - "8300:8300"

            - "8301:8301"

            - "8301:8301/udp"

            - "8302:8302"

            - "8302:8302/udp"

            - "8400:8400"

            - "8500:8500"

            - "8600:8600"

            - "8600:53/udp"


dm2



version: '2'



services:

    consul-server:

        image: consul:latest

        networks:

            - back

        command:

            agent

            -node consul-02

            -server

            -client 0.0.0.0

            -bootstrap-expect 3

            -retry-join ${CONSUL_BOOTSTRAP_IP}

            -advertise ${HOST_IP}

        ports:

            - "8300:8300"

            - "8301:8301"

            - "8301:8301/udp"

            - "8302:8302"

            - "8302:8302/udp"

            - "8400:8400"

            - "8500:8500"

            - "8600:8600"

            - "8600:53/udp"


dm3



version: '2'



services:

    consul-server:

        image: consul:latest

        networks:

            - back

        command:

            agent

            -node consul-03

            -server

            -client 0.0.0.0

            -bootstrap-expect 3

            -retry-join ${CONSUL_BOOTSTRAP_IP}

            -advertise ${HOST_IP}

        ports:

            - "8300:8300"

            - "8301:8301"

            - "8301:8301/udp"

            - "8302:8302"

            - "8302:8302/udp"

            - "8400:8400"

            - "8500:8500"

            - "8600:8600"

            - "8600:53/udp"





docker docker-compose consul







share|improve this question



























    0















    Due to company restrictions I cannot use docker-swarm, so I am trying to setup a consul cluster on multiple machines sharing the same host network, let's pretend these are the 3 machines addresses (I am using virtualbox with docker-machine for testing), these IP are known as HOST_IP by their containers:





    • dm1: 192.168.99.100


    • dm2: 192.168.99.101


    • dm3: 192.168.99.102


    CONSUL_BOOTSTRAP_IP is the main consul bootstrap server 192.168.99.100.



    This setup works (I get the 3 nodes up and running in the web UI) but I get some weird logs in the containers:



    consul-server_1_46f1167db7a9 |     2018/11/14 08:06:48 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host
    
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:50 [WARN] consul: error getting server health from "64bbf570ff39": context deadline exceeded
    
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:51 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host
    
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:52 [WARN] consul: error getting server health from "64bbf570ff39": context deadline exceeded
    
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:53 [WARN] consul: error getting server health from "64bbf570ff39": last request still outstanding
    
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:54 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host


    Why is consul trying to access the docker container internal IP 172.18.0.* instead of using the -advertise address ? This is annoying and in the UI I can see some ghost nodes appearing and disappearing with an error status.



    Here are my compose files:



    dm1



    version: '2'
    

    
services:
    
    consul-server:
    
        image: consul:latest
    
        networks:
    
            - back
    
        command:
    
            agent
    
            -node consul-01
    
            -server
    
            -client 0.0.0.0
    
            -bootstrap-expect 3
    
            -ui
    
            -advertise ${HOST_IP}
    
        ports:
    
            - "8300:8300"
    
            - "8301:8301"
    
            - "8301:8301/udp"
    
            - "8302:8302"
    
            - "8302:8302/udp"
    
            - "8400:8400"
    
            - "8500:8500"
    
            - "8600:8600"
    
            - "8600:53/udp"


    dm2



    version: '2'
    

    
services:
    
    consul-server:
    
        image: consul:latest
    
        networks:
    
            - back
    
        command:
    
            agent
    
            -node consul-02
    
            -server
    
            -client 0.0.0.0
    
            -bootstrap-expect 3
    
            -retry-join ${CONSUL_BOOTSTRAP_IP}
    
            -advertise ${HOST_IP}
    
        ports:
    
            - "8300:8300"
    
            - "8301:8301"
    
            - "8301:8301/udp"
    
            - "8302:8302"
    
            - "8302:8302/udp"
    
            - "8400:8400"
    
            - "8500:8500"
    
            - "8600:8600"
    
            - "8600:53/udp"


    dm3



    version: '2'
    

    
services:
    
    consul-server:
    
        image: consul:latest
    
        networks:
    
            - back
    
        command:
    
            agent
    
            -node consul-03
    
            -server
    
            -client 0.0.0.0
    
            -bootstrap-expect 3
    
            -retry-join ${CONSUL_BOOTSTRAP_IP}
    
            -advertise ${HOST_IP}
    
        ports:
    
            - "8300:8300"
    
            - "8301:8301"
    
            - "8301:8301/udp"
    
            - "8302:8302"
    
            - "8302:8302/udp"
    
            - "8400:8400"
    
            - "8500:8500"
    
            - "8600:8600"
    
            - "8600:53/udp"





    docker docker-compose consul







    share|improve this question

























      0












      0








      0








      Due to company restrictions I cannot use docker-swarm, so I am trying to setup a consul cluster on multiple machines sharing the same host network, let's pretend these are the 3 machines addresses (I am using virtualbox with docker-machine for testing), these IP are known as HOST_IP by their containers:





      • dm1: 192.168.99.100


      • dm2: 192.168.99.101


      • dm3: 192.168.99.102


      CONSUL_BOOTSTRAP_IP is the main consul bootstrap server 192.168.99.100.



      This setup works (I get the 3 nodes up and running in the web UI) but I get some weird logs in the containers:



      consul-server_1_46f1167db7a9 |     2018/11/14 08:06:48 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:50 [WARN] consul: error getting server health from "64bbf570ff39": context deadline exceeded
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:51 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:52 [WARN] consul: error getting server health from "64bbf570ff39": context deadline exceeded
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:53 [WARN] consul: error getting server health from "64bbf570ff39": last request still outstanding
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:54 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host


      Why is consul trying to access the docker container internal IP 172.18.0.* instead of using the -advertise address ? This is annoying and in the UI I can see some ghost nodes appearing and disappearing with an error status.



      Here are my compose files:



      dm1



      version: '2'
      

      
services:
      
    consul-server:
      
        image: consul:latest
      
        networks:
      
            - back
      
        command:
      
            agent
      
            -node consul-01
      
            -server
      
            -client 0.0.0.0
      
            -bootstrap-expect 3
      
            -ui
      
            -advertise ${HOST_IP}
      
        ports:
      
            - "8300:8300"
      
            - "8301:8301"
      
            - "8301:8301/udp"
      
            - "8302:8302"
      
            - "8302:8302/udp"
      
            - "8400:8400"
      
            - "8500:8500"
      
            - "8600:8600"
      
            - "8600:53/udp"


      dm2



      version: '2'
      

      
services:
      
    consul-server:
      
        image: consul:latest
      
        networks:
      
            - back
      
        command:
      
            agent
      
            -node consul-02
      
            -server
      
            -client 0.0.0.0
      
            -bootstrap-expect 3
      
            -retry-join ${CONSUL_BOOTSTRAP_IP}
      
            -advertise ${HOST_IP}
      
        ports:
      
            - "8300:8300"
      
            - "8301:8301"
      
            - "8301:8301/udp"
      
            - "8302:8302"
      
            - "8302:8302/udp"
      
            - "8400:8400"
      
            - "8500:8500"
      
            - "8600:8600"
      
            - "8600:53/udp"


      dm3



      version: '2'
      

      
services:
      
    consul-server:
      
        image: consul:latest
      
        networks:
      
            - back
      
        command:
      
            agent
      
            -node consul-03
      
            -server
      
            -client 0.0.0.0
      
            -bootstrap-expect 3
      
            -retry-join ${CONSUL_BOOTSTRAP_IP}
      
            -advertise ${HOST_IP}
      
        ports:
      
            - "8300:8300"
      
            - "8301:8301"
      
            - "8301:8301/udp"
      
            - "8302:8302"
      
            - "8302:8302/udp"
      
            - "8400:8400"
      
            - "8500:8500"
      
            - "8600:8600"
      
            - "8600:53/udp"





      docker docker-compose consul







      share|improve this question














      Due to company restrictions I cannot use docker-swarm, so I am trying to setup a consul cluster on multiple machines sharing the same host network, let's pretend these are the 3 machines addresses (I am using virtualbox with docker-machine for testing), these IP are known as HOST_IP by their containers:





      • dm1: 192.168.99.100


      • dm2: 192.168.99.101


      • dm3: 192.168.99.102


      CONSUL_BOOTSTRAP_IP is the main consul bootstrap server 192.168.99.100.



      This setup works (I get the 3 nodes up and running in the web UI) but I get some weird logs in the containers:



      consul-server_1_46f1167db7a9 |     2018/11/14 08:06:48 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:50 [WARN] consul: error getting server health from "64bbf570ff39": context deadline exceeded
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:51 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:52 [WARN] consul: error getting server health from "64bbf570ff39": context deadline exceeded
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:53 [WARN] consul: error getting server health from "64bbf570ff39": last request still outstanding
      
consul-server_1_46f1167db7a9 |     2018/11/14 08:06:54 [WARN] consul: error getting server health from "64bbf570ff39": rpc error getting client: failed to get conn: dial tcp <nil>->172.18.0.2:8300: connect: no route to host


      Why is consul trying to access the docker container internal IP 172.18.0.* instead of using the -advertise address ? This is annoying and in the UI I can see some ghost nodes appearing and disappearing with an error status.



      Here are my compose files:



      dm1



      version: '2'
      

      
services:
      
    consul-server:
      
        image: consul:latest
      
        networks:
      
            - back
      
        command:
      
            agent
      
            -node consul-01
      
            -server
      
            -client 0.0.0.0
      
            -bootstrap-expect 3
      
            -ui
      
            -advertise ${HOST_IP}
      
        ports:
      
            - "8300:8300"
      
            - "8301:8301"
      
            - "8301:8301/udp"
      
            - "8302:8302"
      
            - "8302:8302/udp"
      
            - "8400:8400"
      
            - "8500:8500"
      
            - "8600:8600"
      
            - "8600:53/udp"


      dm2



      version: '2'
      

      
services:
      
    consul-server:
      
        image: consul:latest
      
        networks:
      
            - back
      
        command:
      
            agent
      
            -node consul-02
      
            -server
      
            -client 0.0.0.0
      
            -bootstrap-expect 3
      
            -retry-join ${CONSUL_BOOTSTRAP_IP}
      
            -advertise ${HOST_IP}
      
        ports:
      
            - "8300:8300"
      
            - "8301:8301"
      
            - "8301:8301/udp"
      
            - "8302:8302"
      
            - "8302:8302/udp"
      
            - "8400:8400"
      
            - "8500:8500"
      
            - "8600:8600"
      
            - "8600:53/udp"


      dm3



      version: '2'
      

      
services:
      
    consul-server:
      
        image: consul:latest
      
        networks:
      
            - back
      
        command:
      
            agent
      
            -node consul-03
      
            -server
      
            -client 0.0.0.0
      
            -bootstrap-expect 3
      
            -retry-join ${CONSUL_BOOTSTRAP_IP}
      
            -advertise ${HOST_IP}
      
        ports:
      
            - "8300:8300"
      
            - "8301:8301"
      
            - "8301:8301/udp"
      
            - "8302:8302"
      
            - "8302:8302/udp"
      
            - "8400:8400"
      
            - "8500:8500"
      
            - "8600:8600"
      
            - "8600:53/udp"





      docker docker-compose consul




      docker docker-compose consul






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 14 '18 at 8:09









      kitenseikitensei

      1,34012355




      1,34012355
























          0






          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',
          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%2f53295572%2fdocker-consul-cluster-without-swarm%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295572%2fdocker-consul-cluster-without-swarm%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







          -

          這個網誌中的熱門文章

          Hercules Kyvelos

          圖片
          Hercules Kyvelos Statistics Real name Hercules Kyvelos Nickname(s) The God Weight(s) Middleweight Light Middleweight Welterweight Height 5 ft 10 in (180 cm) Reach 72 in (183 cm) Nationality Canadian Born ( 1975-02-25 ) February 25, 1975 (age 43) Montreal, Quebec Stance Orthodox Boxing record Total fights 27 Wins 24 Wins by KO 12 Losses 3 Draws 0 No contests 0 Hercules Kyvelos Medal record Men's Boxing Representing   Canada Pan American Games 1995 Mar del Plata Welterweight Hercules Kyvelos (born February 25, 1975) is a Greek-Canadian boxer in the Welterweight division and is the former Canadian Welterweight Champion. [1] He fought at the 1996 Summer Olympics in Atlanta, Georgia. Contents 1 Early life 2 Amateur career 3 Pro career 3.1 WBO Welterweight Championship 3.2 Personal life 4 References 5 External links Early life Hercules was born in
          閱讀完整內容

          Tangent Lines Diagram Along Smooth Curve

          圖片
          7 1 I am trying to replicate a diagram and have a minimal example. I don't know how to add additional tangents between the specified points and preserve smoothness. documentclass{article} usepackage{tikz} usetikzlibrary{calc,intersections} begin{document} begin{tikzpicture} % Axes draw [->, name path=x] (-1,0) -- (11,0) node [right] {$x$}; draw [->] (0,-1) -- (0,6) node [above] {$y$}; % Origin node at (0,0) [below left] {$0$}; % Points coordinate (start) at (1,-0.8); coordinate (c1) at (3,3); coordinate (c2) at (5.5,1.5); coordinate (c3) at (8,4); coordinate (end) at (10.5,-0.8); % show the points foreach n in {start,c1,c2,c3,end} fill [black] (n) circle (2pt) node [below] {}; % join the coordinates draw [thick,name path=curve] (start) to[out=70,in=180] (c1) to[out=0,in=180]
          閱讀完整內容

          Yusuf al-Mu'taman ibn Hud

          圖片
          Main article: Taifa of Zaragoza Al-Mu'taman Ruler of Zaragoza Reign 1081–1085 Predecessor Ahmad al-Muqtadir Successor Al-Mustain II Born Zaragoza Died 1085 Full name Yusuf ibn Ahmad al-Mu'taman ibn Hūd House Banu Hud Yusuf ibn Ahmad al-Mu'taman ibn Hūd (Arabic: المؤتمن بالله يوسف إبن أحمد إبن هود ‎, al-Mutaman bi l-Lah , died c. 1085) was the third king of the Banu Hud dynasty who ruled over the Taifa of Zaragoza from 1081 to 1085. Yusuf al-Mutaman reigned during the height of power of Muslim Zaragoza , following the thriving period of his father Ahmad al-Muqtadir. He continued his father's efforts and created around him a court of intellectuals, living in the beautiful palace of Aljafería, nicknamed as "the palace of joy". Al-Mu'taman was also a scholarly king and a patron of science, philosophy and arts. As an example of a wise king, he knew astrology, philosophy, and especially mathematics, a discipline in which
          閱讀完整內容