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
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