How to get rid of cloud-init?












11















I'm using Ubuntu 14.04 image as my base box for vagrant. Unfortunately this base box contains cloud-init which causes many problems during starting-up the machine: https://github.com/mitchellh/vagrant/issues/3860



I'm not using my machine in the cloud so I don't really need this. I though typing:



sudo apt-get remove cloud-init


will solve my problems but the machine still spend about 3 minutes on startup trying to configure something I don't need.



I can see there a a number of cloud-init related files in /etc/init (for example cloud-init.conf, cloud-final.conf, cloud-config.conf etc). I could delete them but I'm not sure if this is safe.



I've also installed rcconf to check all starup scripts but I can't find anything related to cloud-init there. Any ideas?










share|improve this question



























    11















    I'm using Ubuntu 14.04 image as my base box for vagrant. Unfortunately this base box contains cloud-init which causes many problems during starting-up the machine: https://github.com/mitchellh/vagrant/issues/3860



    I'm not using my machine in the cloud so I don't really need this. I though typing:



    sudo apt-get remove cloud-init


    will solve my problems but the machine still spend about 3 minutes on startup trying to configure something I don't need.



    I can see there a a number of cloud-init related files in /etc/init (for example cloud-init.conf, cloud-final.conf, cloud-config.conf etc). I could delete them but I'm not sure if this is safe.



    I've also installed rcconf to check all starup scripts but I can't find anything related to cloud-init there. Any ideas?










    share|improve this question

























      11












      11








      11


      0






      I'm using Ubuntu 14.04 image as my base box for vagrant. Unfortunately this base box contains cloud-init which causes many problems during starting-up the machine: https://github.com/mitchellh/vagrant/issues/3860



      I'm not using my machine in the cloud so I don't really need this. I though typing:



      sudo apt-get remove cloud-init


      will solve my problems but the machine still spend about 3 minutes on startup trying to configure something I don't need.



      I can see there a a number of cloud-init related files in /etc/init (for example cloud-init.conf, cloud-final.conf, cloud-config.conf etc). I could delete them but I'm not sure if this is safe.



      I've also installed rcconf to check all starup scripts but I can't find anything related to cloud-init there. Any ideas?










      share|improve this question














      I'm using Ubuntu 14.04 image as my base box for vagrant. Unfortunately this base box contains cloud-init which causes many problems during starting-up the machine: https://github.com/mitchellh/vagrant/issues/3860



      I'm not using my machine in the cloud so I don't really need this. I though typing:



      sudo apt-get remove cloud-init


      will solve my problems but the machine still spend about 3 minutes on startup trying to configure something I don't need.



      I can see there a a number of cloud-init related files in /etc/init (for example cloud-init.conf, cloud-final.conf, cloud-config.conf etc). I could delete them but I'm not sure if this is safe.



      I've also installed rcconf to check all starup scripts but I can't find anything related to cloud-init there. Any ideas?







      uninstall startup cloud init init.d






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 20 '14 at 9:14









      mnowotkamnowotka

      2001311




      2001311






















          4 Answers
          4






          active

          oldest

          votes


















          6














          On 14.04 you can use dpkg-reconfigure to disable cloud-init in the following way:



          echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg
          sudo dpkg-reconfigure -f noninteractive cloud-init


          or just use sudo dpkg-reconfigure cloud-init to do it interactively.






          share|improve this answer































            4














            According to the cloud-init docs the way to disable it is:



            sudo touch /etc/cloud/cloud-init.disabled


            And/or set cloud-init=disabled on the kernel command line if it's enabled that way.






            share|improve this answer
























            • Note that it does not remove it. It is still there but it will stop trying to configure stuff at a very early stage. See cloudinit.readthedocs.io/en/latest/topics/boot.html

              – Ludovic Kuty
              Mar 13 at 7:41











            • Sure that's why I said it would disable it.

              – Pierz
              Mar 13 at 21:33











            • Yes you are right. My comment is useless.

              – Ludovic Kuty
              Mar 14 at 5:30



















            2














            Cloud Init is there to configure networking and it can be stopped at different stages. In recent versions, you can disable Cloud Init at the first stage by making sure the following file exists:



            /etc/cloud/cloud-init.disabled


            or at a later stage by making sure the file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg exists with the following content:



            network: {config: disabled}


            You can use this command for it:



            $ sudo echo "network: {config: disabled}" > /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg


            This information can be found in the header comments of /etc/netplan/50-cloud-init.yaml, which in part read as follows:




            # To disable cloud-init's network configuration capabilities, write a file
            # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
            # network: {config: disabled}



            This is from the file in Ubuntu 18.04 LTS and likely to also be valid for later releases.






            share|improve this answer


























            • IMHO, it only disables its network configuration part. Thus it is not enough.

              – Ludovic Kuty
              Mar 13 at 7:39











            • @LudovicKuty Which is precisely what cloud-init is there to do: configure things. Thus, if you get it to stop trying to configure things, you have accomplished your goal and it is enough to make it stay out of your way. If you insist it isn't, then please explain what "enough" would be, exactly.

              – code_dredd
              Mar 13 at 8:55











            • It might still tries to configure other stuff than networking. IMHO the OP wanted to disable it completely. Note that this granularity might be interesting in other cases.

              – Ludovic Kuty
              Mar 13 at 9:02













            • @LudovicKuty Your comments are coming across as speculative ("IMHO", "it might ...", etc). Unless you can show that the documentation is wrong and that it does continue to try things after being told not to, I don't think there's much more to this, and in that case, you'd be better off reporting a bug to them. This has been enough every time I've done it in my servers.

              – code_dredd
              Mar 13 at 9:11











            • Go check cloudinit.readthedocs.io/en/latest/topics/boot.html vs cloudinit.readthedocs.io/en/latest/topics/network-config.html. You're criticizing my "IMHO" and "might" and you're writing "the correct way to disable Cloud Init is with this command" but you should have added "IMHO" since it is not the correct way to do it.

              – Ludovic Kuty
              Mar 13 at 9:12





















            1














            This worked for me in Ubuntu Server 18.04.1 LST




            1. $ echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg


            2. $ sudo apt-get purge cloud-init


            3. $ sudo rm -rf /etc/cloud/; sudo rm -rf /var/lib/cloud/


            4. $ reboot



            Good Luck.






            share|improve this answer


























            • Really? Changig a file you delete two steps later? Seems like you can skip the first step.

              – Enno Gröper
              Feb 20 at 13:19











            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%2f539277%2fhow-to-get-rid-of-cloud-init%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            4 Answers
            4






            active

            oldest

            votes








            4 Answers
            4






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            6














            On 14.04 you can use dpkg-reconfigure to disable cloud-init in the following way:



            echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg
            sudo dpkg-reconfigure -f noninteractive cloud-init


            or just use sudo dpkg-reconfigure cloud-init to do it interactively.






            share|improve this answer




























              6














              On 14.04 you can use dpkg-reconfigure to disable cloud-init in the following way:



              echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg
              sudo dpkg-reconfigure -f noninteractive cloud-init


              or just use sudo dpkg-reconfigure cloud-init to do it interactively.






              share|improve this answer


























                6












                6








                6







                On 14.04 you can use dpkg-reconfigure to disable cloud-init in the following way:



                echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg
                sudo dpkg-reconfigure -f noninteractive cloud-init


                or just use sudo dpkg-reconfigure cloud-init to do it interactively.






                share|improve this answer













                On 14.04 you can use dpkg-reconfigure to disable cloud-init in the following way:



                echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg
                sudo dpkg-reconfigure -f noninteractive cloud-init


                or just use sudo dpkg-reconfigure cloud-init to do it interactively.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 29 '15 at 15:28









                m1keilm1keil

                16112




                16112

























                    4














                    According to the cloud-init docs the way to disable it is:



                    sudo touch /etc/cloud/cloud-init.disabled


                    And/or set cloud-init=disabled on the kernel command line if it's enabled that way.






                    share|improve this answer
























                    • Note that it does not remove it. It is still there but it will stop trying to configure stuff at a very early stage. See cloudinit.readthedocs.io/en/latest/topics/boot.html

                      – Ludovic Kuty
                      Mar 13 at 7:41











                    • Sure that's why I said it would disable it.

                      – Pierz
                      Mar 13 at 21:33











                    • Yes you are right. My comment is useless.

                      – Ludovic Kuty
                      Mar 14 at 5:30
















                    4














                    According to the cloud-init docs the way to disable it is:



                    sudo touch /etc/cloud/cloud-init.disabled


                    And/or set cloud-init=disabled on the kernel command line if it's enabled that way.






                    share|improve this answer
























                    • Note that it does not remove it. It is still there but it will stop trying to configure stuff at a very early stage. See cloudinit.readthedocs.io/en/latest/topics/boot.html

                      – Ludovic Kuty
                      Mar 13 at 7:41











                    • Sure that's why I said it would disable it.

                      – Pierz
                      Mar 13 at 21:33











                    • Yes you are right. My comment is useless.

                      – Ludovic Kuty
                      Mar 14 at 5:30














                    4












                    4








                    4







                    According to the cloud-init docs the way to disable it is:



                    sudo touch /etc/cloud/cloud-init.disabled


                    And/or set cloud-init=disabled on the kernel command line if it's enabled that way.






                    share|improve this answer













                    According to the cloud-init docs the way to disable it is:



                    sudo touch /etc/cloud/cloud-init.disabled


                    And/or set cloud-init=disabled on the kernel command line if it's enabled that way.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Jun 18 '18 at 13:34









                    PierzPierz

                    92197




                    92197













                    • Note that it does not remove it. It is still there but it will stop trying to configure stuff at a very early stage. See cloudinit.readthedocs.io/en/latest/topics/boot.html

                      – Ludovic Kuty
                      Mar 13 at 7:41











                    • Sure that's why I said it would disable it.

                      – Pierz
                      Mar 13 at 21:33











                    • Yes you are right. My comment is useless.

                      – Ludovic Kuty
                      Mar 14 at 5:30



















                    • Note that it does not remove it. It is still there but it will stop trying to configure stuff at a very early stage. See cloudinit.readthedocs.io/en/latest/topics/boot.html

                      – Ludovic Kuty
                      Mar 13 at 7:41











                    • Sure that's why I said it would disable it.

                      – Pierz
                      Mar 13 at 21:33











                    • Yes you are right. My comment is useless.

                      – Ludovic Kuty
                      Mar 14 at 5:30

















                    Note that it does not remove it. It is still there but it will stop trying to configure stuff at a very early stage. See cloudinit.readthedocs.io/en/latest/topics/boot.html

                    – Ludovic Kuty
                    Mar 13 at 7:41





                    Note that it does not remove it. It is still there but it will stop trying to configure stuff at a very early stage. See cloudinit.readthedocs.io/en/latest/topics/boot.html

                    – Ludovic Kuty
                    Mar 13 at 7:41













                    Sure that's why I said it would disable it.

                    – Pierz
                    Mar 13 at 21:33





                    Sure that's why I said it would disable it.

                    – Pierz
                    Mar 13 at 21:33













                    Yes you are right. My comment is useless.

                    – Ludovic Kuty
                    Mar 14 at 5:30





                    Yes you are right. My comment is useless.

                    – Ludovic Kuty
                    Mar 14 at 5:30











                    2














                    Cloud Init is there to configure networking and it can be stopped at different stages. In recent versions, you can disable Cloud Init at the first stage by making sure the following file exists:



                    /etc/cloud/cloud-init.disabled


                    or at a later stage by making sure the file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg exists with the following content:



                    network: {config: disabled}


                    You can use this command for it:



                    $ sudo echo "network: {config: disabled}" > /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg


                    This information can be found in the header comments of /etc/netplan/50-cloud-init.yaml, which in part read as follows:




                    # To disable cloud-init's network configuration capabilities, write a file
                    # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
                    # network: {config: disabled}



                    This is from the file in Ubuntu 18.04 LTS and likely to also be valid for later releases.






                    share|improve this answer


























                    • IMHO, it only disables its network configuration part. Thus it is not enough.

                      – Ludovic Kuty
                      Mar 13 at 7:39











                    • @LudovicKuty Which is precisely what cloud-init is there to do: configure things. Thus, if you get it to stop trying to configure things, you have accomplished your goal and it is enough to make it stay out of your way. If you insist it isn't, then please explain what "enough" would be, exactly.

                      – code_dredd
                      Mar 13 at 8:55











                    • It might still tries to configure other stuff than networking. IMHO the OP wanted to disable it completely. Note that this granularity might be interesting in other cases.

                      – Ludovic Kuty
                      Mar 13 at 9:02













                    • @LudovicKuty Your comments are coming across as speculative ("IMHO", "it might ...", etc). Unless you can show that the documentation is wrong and that it does continue to try things after being told not to, I don't think there's much more to this, and in that case, you'd be better off reporting a bug to them. This has been enough every time I've done it in my servers.

                      – code_dredd
                      Mar 13 at 9:11











                    • Go check cloudinit.readthedocs.io/en/latest/topics/boot.html vs cloudinit.readthedocs.io/en/latest/topics/network-config.html. You're criticizing my "IMHO" and "might" and you're writing "the correct way to disable Cloud Init is with this command" but you should have added "IMHO" since it is not the correct way to do it.

                      – Ludovic Kuty
                      Mar 13 at 9:12


















                    2














                    Cloud Init is there to configure networking and it can be stopped at different stages. In recent versions, you can disable Cloud Init at the first stage by making sure the following file exists:



                    /etc/cloud/cloud-init.disabled


                    or at a later stage by making sure the file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg exists with the following content:



                    network: {config: disabled}


                    You can use this command for it:



                    $ sudo echo "network: {config: disabled}" > /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg


                    This information can be found in the header comments of /etc/netplan/50-cloud-init.yaml, which in part read as follows:




                    # To disable cloud-init's network configuration capabilities, write a file
                    # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
                    # network: {config: disabled}



                    This is from the file in Ubuntu 18.04 LTS and likely to also be valid for later releases.






                    share|improve this answer


























                    • IMHO, it only disables its network configuration part. Thus it is not enough.

                      – Ludovic Kuty
                      Mar 13 at 7:39











                    • @LudovicKuty Which is precisely what cloud-init is there to do: configure things. Thus, if you get it to stop trying to configure things, you have accomplished your goal and it is enough to make it stay out of your way. If you insist it isn't, then please explain what "enough" would be, exactly.

                      – code_dredd
                      Mar 13 at 8:55











                    • It might still tries to configure other stuff than networking. IMHO the OP wanted to disable it completely. Note that this granularity might be interesting in other cases.

                      – Ludovic Kuty
                      Mar 13 at 9:02













                    • @LudovicKuty Your comments are coming across as speculative ("IMHO", "it might ...", etc). Unless you can show that the documentation is wrong and that it does continue to try things after being told not to, I don't think there's much more to this, and in that case, you'd be better off reporting a bug to them. This has been enough every time I've done it in my servers.

                      – code_dredd
                      Mar 13 at 9:11











                    • Go check cloudinit.readthedocs.io/en/latest/topics/boot.html vs cloudinit.readthedocs.io/en/latest/topics/network-config.html. You're criticizing my "IMHO" and "might" and you're writing "the correct way to disable Cloud Init is with this command" but you should have added "IMHO" since it is not the correct way to do it.

                      – Ludovic Kuty
                      Mar 13 at 9:12
















                    2












                    2








                    2







                    Cloud Init is there to configure networking and it can be stopped at different stages. In recent versions, you can disable Cloud Init at the first stage by making sure the following file exists:



                    /etc/cloud/cloud-init.disabled


                    or at a later stage by making sure the file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg exists with the following content:



                    network: {config: disabled}


                    You can use this command for it:



                    $ sudo echo "network: {config: disabled}" > /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg


                    This information can be found in the header comments of /etc/netplan/50-cloud-init.yaml, which in part read as follows:




                    # To disable cloud-init's network configuration capabilities, write a file
                    # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
                    # network: {config: disabled}



                    This is from the file in Ubuntu 18.04 LTS and likely to also be valid for later releases.






                    share|improve this answer















                    Cloud Init is there to configure networking and it can be stopped at different stages. In recent versions, you can disable Cloud Init at the first stage by making sure the following file exists:



                    /etc/cloud/cloud-init.disabled


                    or at a later stage by making sure the file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg exists with the following content:



                    network: {config: disabled}


                    You can use this command for it:



                    $ sudo echo "network: {config: disabled}" > /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg


                    This information can be found in the header comments of /etc/netplan/50-cloud-init.yaml, which in part read as follows:




                    # To disable cloud-init's network configuration capabilities, write a file
                    # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
                    # network: {config: disabled}



                    This is from the file in Ubuntu 18.04 LTS and likely to also be valid for later releases.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Mar 15 at 21:57

























                    answered May 3 '18 at 16:18









                    code_dreddcode_dredd

                    5782415




                    5782415













                    • IMHO, it only disables its network configuration part. Thus it is not enough.

                      – Ludovic Kuty
                      Mar 13 at 7:39











                    • @LudovicKuty Which is precisely what cloud-init is there to do: configure things. Thus, if you get it to stop trying to configure things, you have accomplished your goal and it is enough to make it stay out of your way. If you insist it isn't, then please explain what "enough" would be, exactly.

                      – code_dredd
                      Mar 13 at 8:55











                    • It might still tries to configure other stuff than networking. IMHO the OP wanted to disable it completely. Note that this granularity might be interesting in other cases.

                      – Ludovic Kuty
                      Mar 13 at 9:02













                    • @LudovicKuty Your comments are coming across as speculative ("IMHO", "it might ...", etc). Unless you can show that the documentation is wrong and that it does continue to try things after being told not to, I don't think there's much more to this, and in that case, you'd be better off reporting a bug to them. This has been enough every time I've done it in my servers.

                      – code_dredd
                      Mar 13 at 9:11











                    • Go check cloudinit.readthedocs.io/en/latest/topics/boot.html vs cloudinit.readthedocs.io/en/latest/topics/network-config.html. You're criticizing my "IMHO" and "might" and you're writing "the correct way to disable Cloud Init is with this command" but you should have added "IMHO" since it is not the correct way to do it.

                      – Ludovic Kuty
                      Mar 13 at 9:12





















                    • IMHO, it only disables its network configuration part. Thus it is not enough.

                      – Ludovic Kuty
                      Mar 13 at 7:39











                    • @LudovicKuty Which is precisely what cloud-init is there to do: configure things. Thus, if you get it to stop trying to configure things, you have accomplished your goal and it is enough to make it stay out of your way. If you insist it isn't, then please explain what "enough" would be, exactly.

                      – code_dredd
                      Mar 13 at 8:55











                    • It might still tries to configure other stuff than networking. IMHO the OP wanted to disable it completely. Note that this granularity might be interesting in other cases.

                      – Ludovic Kuty
                      Mar 13 at 9:02













                    • @LudovicKuty Your comments are coming across as speculative ("IMHO", "it might ...", etc). Unless you can show that the documentation is wrong and that it does continue to try things after being told not to, I don't think there's much more to this, and in that case, you'd be better off reporting a bug to them. This has been enough every time I've done it in my servers.

                      – code_dredd
                      Mar 13 at 9:11











                    • Go check cloudinit.readthedocs.io/en/latest/topics/boot.html vs cloudinit.readthedocs.io/en/latest/topics/network-config.html. You're criticizing my "IMHO" and "might" and you're writing "the correct way to disable Cloud Init is with this command" but you should have added "IMHO" since it is not the correct way to do it.

                      – Ludovic Kuty
                      Mar 13 at 9:12



















                    IMHO, it only disables its network configuration part. Thus it is not enough.

                    – Ludovic Kuty
                    Mar 13 at 7:39





                    IMHO, it only disables its network configuration part. Thus it is not enough.

                    – Ludovic Kuty
                    Mar 13 at 7:39













                    @LudovicKuty Which is precisely what cloud-init is there to do: configure things. Thus, if you get it to stop trying to configure things, you have accomplished your goal and it is enough to make it stay out of your way. If you insist it isn't, then please explain what "enough" would be, exactly.

                    – code_dredd
                    Mar 13 at 8:55





                    @LudovicKuty Which is precisely what cloud-init is there to do: configure things. Thus, if you get it to stop trying to configure things, you have accomplished your goal and it is enough to make it stay out of your way. If you insist it isn't, then please explain what "enough" would be, exactly.

                    – code_dredd
                    Mar 13 at 8:55













                    It might still tries to configure other stuff than networking. IMHO the OP wanted to disable it completely. Note that this granularity might be interesting in other cases.

                    – Ludovic Kuty
                    Mar 13 at 9:02







                    It might still tries to configure other stuff than networking. IMHO the OP wanted to disable it completely. Note that this granularity might be interesting in other cases.

                    – Ludovic Kuty
                    Mar 13 at 9:02















                    @LudovicKuty Your comments are coming across as speculative ("IMHO", "it might ...", etc). Unless you can show that the documentation is wrong and that it does continue to try things after being told not to, I don't think there's much more to this, and in that case, you'd be better off reporting a bug to them. This has been enough every time I've done it in my servers.

                    – code_dredd
                    Mar 13 at 9:11





                    @LudovicKuty Your comments are coming across as speculative ("IMHO", "it might ...", etc). Unless you can show that the documentation is wrong and that it does continue to try things after being told not to, I don't think there's much more to this, and in that case, you'd be better off reporting a bug to them. This has been enough every time I've done it in my servers.

                    – code_dredd
                    Mar 13 at 9:11













                    Go check cloudinit.readthedocs.io/en/latest/topics/boot.html vs cloudinit.readthedocs.io/en/latest/topics/network-config.html. You're criticizing my "IMHO" and "might" and you're writing "the correct way to disable Cloud Init is with this command" but you should have added "IMHO" since it is not the correct way to do it.

                    – Ludovic Kuty
                    Mar 13 at 9:12







                    Go check cloudinit.readthedocs.io/en/latest/topics/boot.html vs cloudinit.readthedocs.io/en/latest/topics/network-config.html. You're criticizing my "IMHO" and "might" and you're writing "the correct way to disable Cloud Init is with this command" but you should have added "IMHO" since it is not the correct way to do it.

                    – Ludovic Kuty
                    Mar 13 at 9:12













                    1














                    This worked for me in Ubuntu Server 18.04.1 LST




                    1. $ echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg


                    2. $ sudo apt-get purge cloud-init


                    3. $ sudo rm -rf /etc/cloud/; sudo rm -rf /var/lib/cloud/


                    4. $ reboot



                    Good Luck.






                    share|improve this answer


























                    • Really? Changig a file you delete two steps later? Seems like you can skip the first step.

                      – Enno Gröper
                      Feb 20 at 13:19
















                    1














                    This worked for me in Ubuntu Server 18.04.1 LST




                    1. $ echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg


                    2. $ sudo apt-get purge cloud-init


                    3. $ sudo rm -rf /etc/cloud/; sudo rm -rf /var/lib/cloud/


                    4. $ reboot



                    Good Luck.






                    share|improve this answer


























                    • Really? Changig a file you delete two steps later? Seems like you can skip the first step.

                      – Enno Gröper
                      Feb 20 at 13:19














                    1












                    1








                    1







                    This worked for me in Ubuntu Server 18.04.1 LST




                    1. $ echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg


                    2. $ sudo apt-get purge cloud-init


                    3. $ sudo rm -rf /etc/cloud/; sudo rm -rf /var/lib/cloud/


                    4. $ reboot



                    Good Luck.






                    share|improve this answer















                    This worked for me in Ubuntu Server 18.04.1 LST




                    1. $ echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg


                    2. $ sudo apt-get purge cloud-init


                    3. $ sudo rm -rf /etc/cloud/; sudo rm -rf /var/lib/cloud/


                    4. $ reboot



                    Good Luck.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Aug 27 '18 at 18:42

























                    answered Aug 24 '18 at 15:06









                    Lion GatesLion Gates

                    93




                    93













                    • Really? Changig a file you delete two steps later? Seems like you can skip the first step.

                      – Enno Gröper
                      Feb 20 at 13:19



















                    • Really? Changig a file you delete two steps later? Seems like you can skip the first step.

                      – Enno Gröper
                      Feb 20 at 13:19

















                    Really? Changig a file you delete two steps later? Seems like you can skip the first step.

                    – Enno Gröper
                    Feb 20 at 13:19





                    Really? Changig a file you delete two steps later? Seems like you can skip the first step.

                    – Enno Gröper
                    Feb 20 at 13:19


















                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f539277%2fhow-to-get-rid-of-cloud-init%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

                    數位音樂下載

                    格利澤436b

                    When can things happen in Etherscan, such as the picture below?