Create an empty file to prevent the service from starting
sudo touch /etc/cloud/cloud-init.disabled
Disable all services (uncheck everything except "None"):
sudo dpkg-reconfigure cloud-init
Uninstall the package and delete the folders
sudo dpkg-reconfigure cloud-init
sudo apt-get purge cloud-init
sudo rm -rf /etc/cloud/ && sudo rm -rf /var/lib/cloud/
Restart the computer
sudo reboot
This instruction no longer works, the errors you will get are: dpkg-reconfigure cloud-init (must be run from root)
If you type sudo in front of that command you will get into the cloud-init but you cannot select anything
Please update the instructions
It works for me. Except that it has to be "sudo dpkg-reconfigure cloud-init".
Apart from that, it works. Just removed it from 4 servers.
This instruction no longer works, the errors you will get are: dpkg-reconfigure cloud-init (must be run from root)
If you type sudo in front of that command you will get into the cloud-init but you cannot select anything
Please update the instructions
it worked here!
Ubuntu 20.04.2 LTS
This instruction no longer works, the errors you will get are: dpkg-reconfigure cloud-init (must be run from root)
If you type sudo in front of that command you will get into the cloud-init but you cannot select anything
Please update the instructionsIt works for me. Except that it has to be "sudo dpkg-reconfigure cloud-init".
Apart from that, it works. Just removed it from 4 servers.
Yes, add sudo and works for me
❤️
Thanks!
works here ubuntu with su (root) server 20.04 rasbian mate rasberry pi4 8g
works like a charm here (Ubuntu 20.04.6)
Works on 21.10 Ubuntu server.
Works on Debian 11, thanks
works on 22.04 Ubuntu server, thanks a lot!
Working on ubuntu server 22.04, thanks!
"Stupid Question": Should sudo apt-get purge cloud-init not be enough?
If not, I would say its bad packaging of cloud-init and should be handled as a clound-init bug.
"Stupid Question": Should
sudo apt-get purge cloud-initnot be enough?
If not, I would say its bad packaging of cloud-init and should be handled as a clound-init bug.
the folders /etc/cloud/ and /var/lib/cloud/ are not empty after sudo apt-get purge cloud-init - they still contain a bunch of config files - otherwise it is sufficient.
Uninstalling on Ubuntu 22.04 marks neccessary packages like netplan.io for autoremove. you should mark them firs as manual before removing cloud-init
Fordp12 -> P.I.C.N.I.C.
(Problem in chair, not in computer)
Uninstalling on Ubuntu 22.04 marks neccessary packages like netplan.io for autoremove. you should mark them firs as manual before removing cloud-init
I second that. There is no actual reason to delete the cloud init from the server. Once you have the file touched and have the service disabled/stopped it isn't relevant as to whether it is installed or not. It will NEVER run.
While I concur that installation is irrelevant after the service is disabled by the dpkg-reconfigure edits, netplan.io was left alone on my recent 22.04 install after apt purge cloud-init.
@zoilomora, muchas gracias.
works fine on ubuntu 22.04.2 LTS
Works like a charm, thank you very much ♥
While I concur that installation is irrelevant after the service is disabled by the dpkg-reconfigure edits, netplan.io was left alone on my recent 22.04 install after apt purge cloud-init.
@zoilomora, muchas gracias.
While it does leave netplan.io and some other rather necessary things alone if you EVER run 'sudo apt autoremove' for any reason in the future you will cripple the install. Hope you have physical access or IPMI to fix it at that point.
Because of this I would never run anything more than 'sudo touch /etc/cloud/cloud-init.disabled'.
Really stupid move on Ubuntu's part to tie things in like this for a service not everyone is going to use. I hate opt-out with the fury of 9001 dying suns.
While it does leave netplan.io and some other rather necessary things alone if you EVER run 'sudo apt autoremove' for any reason in the future you will cripple the install. Hope you have physical access or IPMI to fix it at that point.
Because of this I would never run anything more than 'sudo touch /etc/cloud/cloud-init.disabled'.
Strongly agree on this one. Creating the file does the job, and causes no further unforeseen issues.
I have an 22.04.3 minimal-server vm.
I purged cloud-init, and did an autoremove afterwards.
Nothing bad happen. All works fine as before. netplan is still marked as automatic installed and active/working.
Only a few python3-packages are removed, as they are (correctly) not needed by an package anymore.
So, for my conclusion.
sudo touch /etc/cloud/cloud-init.disabled is enough if you just don't need it, but doesn't care about some unused stuff left on disk.
apt-get purge cloud-init if you want to remove it.
This instruction no longer works, the errors you will get are: dpkg-reconfigure cloud-init (must be run from root)
If you type sudo in front of that command you will get into the cloud-init but you cannot select anything
Please update the instructions