Docker breaks network bridging to virtual machines












0














After installing docker I can no longer access my VMs running on my Linux machine. The VMs are up and running but other hosts can no longer access them at all. Has anybody already encountered this problem before and could help with these two questions?




  • Why is this the case?

  • How can I reconfigure my system to again correctly bridge to the VMs?










share|improve this question



























    0














    After installing docker I can no longer access my VMs running on my Linux machine. The VMs are up and running but other hosts can no longer access them at all. Has anybody already encountered this problem before and could help with these two questions?




    • Why is this the case?

    • How can I reconfigure my system to again correctly bridge to the VMs?










    share|improve this question

























      0












      0








      0







      After installing docker I can no longer access my VMs running on my Linux machine. The VMs are up and running but other hosts can no longer access them at all. Has anybody already encountered this problem before and could help with these two questions?




      • Why is this the case?

      • How can I reconfigure my system to again correctly bridge to the VMs?










      share|improve this question













      After installing docker I can no longer access my VMs running on my Linux machine. The VMs are up and running but other hosts can no longer access them at all. Has anybody already encountered this problem before and could help with these two questions?




      • Why is this the case?

      • How can I reconfigure my system to again correctly bridge to the VMs?







      networking kvm docker






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 8 at 23:19









      Regis May

      2191311




      2191311






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Sadly Docker breaks bridge networking by changing the system's IPTABLES firewalls when it starts. This is a known problem without a decent solution.



          See:
          https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865975



          A solution from here is:
          https://anteru.net/blog/2017/docker-kvm-and-iptables/index.html



          Create a file /etc/docker/daemon.json with the following contents:



          {
          "iptables" : false
          }


          WARNING: This "fix" may have serious security implications so beware. I think the best solution would be for docker to create and manage its own chains in IPTABLES and leave the system ones alone.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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%2faskubuntu.com%2fquestions%2f1073501%2fdocker-breaks-network-bridging-to-virtual-machines%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









            0














            Sadly Docker breaks bridge networking by changing the system's IPTABLES firewalls when it starts. This is a known problem without a decent solution.



            See:
            https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865975



            A solution from here is:
            https://anteru.net/blog/2017/docker-kvm-and-iptables/index.html



            Create a file /etc/docker/daemon.json with the following contents:



            {
            "iptables" : false
            }


            WARNING: This "fix" may have serious security implications so beware. I think the best solution would be for docker to create and manage its own chains in IPTABLES and leave the system ones alone.






            share|improve this answer




























              0














              Sadly Docker breaks bridge networking by changing the system's IPTABLES firewalls when it starts. This is a known problem without a decent solution.



              See:
              https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865975



              A solution from here is:
              https://anteru.net/blog/2017/docker-kvm-and-iptables/index.html



              Create a file /etc/docker/daemon.json with the following contents:



              {
              "iptables" : false
              }


              WARNING: This "fix" may have serious security implications so beware. I think the best solution would be for docker to create and manage its own chains in IPTABLES and leave the system ones alone.






              share|improve this answer


























                0












                0








                0






                Sadly Docker breaks bridge networking by changing the system's IPTABLES firewalls when it starts. This is a known problem without a decent solution.



                See:
                https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865975



                A solution from here is:
                https://anteru.net/blog/2017/docker-kvm-and-iptables/index.html



                Create a file /etc/docker/daemon.json with the following contents:



                {
                "iptables" : false
                }


                WARNING: This "fix" may have serious security implications so beware. I think the best solution would be for docker to create and manage its own chains in IPTABLES and leave the system ones alone.






                share|improve this answer














                Sadly Docker breaks bridge networking by changing the system's IPTABLES firewalls when it starts. This is a known problem without a decent solution.



                See:
                https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865975



                A solution from here is:
                https://anteru.net/blog/2017/docker-kvm-and-iptables/index.html



                Create a file /etc/docker/daemon.json with the following contents:



                {
                "iptables" : false
                }


                WARNING: This "fix" may have serious security implications so beware. I think the best solution would be for docker to create and manage its own chains in IPTABLES and leave the system ones alone.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 11 at 15:01

























                answered Dec 11 at 14:46









                mattaw

                11




                11






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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%2faskubuntu.com%2fquestions%2f1073501%2fdocker-breaks-network-bridging-to-virtual-machines%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

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕