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
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.
@qupfer I can confirm it's totally safe to remove cloud-init
Seems I've missed the warnings (if I've seen any) and droped mine on May 23, 2022 on next step after I've googled this gist and my cloud-init has been successfully disabled
Ubuntu 22.04.3, dedicated server at Frankfurt, DE from Hetzner
This worked perfectly thank you!
Hello everyone!
I just wanted to inform you that I've created a bash script designed to automate the process of disabling cloud-init on Ubuntu servers. It's a quick and simple solution you can even call through a oneliner.
GitHub Repo: disable-cloud-init
Give it a try and let me know your thoughts! Your feedback is highly appreciated.
After purged cloud-init (on 22.04), the netplan package is also removed.
I followed this section 3.3. Temporary Static IP via ip
to temporary get an IP address, then reinstall netplan using: sudo apt install netplan.io
After purged cloud-init (on 22.04), the netplan package is also removed. I followed this section 3.3. Temporary Static IP via ip to temporary get an IP address, then reinstall netplan using: sudo apt install netplan.io
Almost had a heart attack...
Thankfully, can confirm that these instructions worked without removing the netplan package for me (Server 22.04).
Hello guys, since the issue with "netplan.io" seems to be affecting more and more people recently I've decided to study a solution that would avoid having to mess with temporary IPs and other stuff.
I've found a quick and dirty workaround everyone can use in case the netplan.io package is installed.
Basically, before proceeding to purge the "cloud-init" package with APT, we can mark the package "netplan.io" as on hold in order to be sure it will not be removed; this will ensure that the "netplan.io" dependency is not touched by APT at all.
The following one-liner can be used before the sudo apt-get purge cloud-init command to check if "netplan.io" is installed and put it on hold automatically: dpkg-query -W -f='${Status}' netplan.io 2>/dev/null | grep -q "install ok installed" && { sudo apt-mark hold netplan.io && echo "netplan.io put on hold"; } || echo "netplan.io is not available";
More informations about apt-mark can be found in the official debian manpage: manpages.debian.org
I've also updated my Bash Script (disable-cloud-init) to include this solution.
Ubuntu 24.04 server (minimal configuration) comes with the following at file /etc/netplan/50-cloud-init.yaml
# 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}
Hello guys, since the issue with "netplan.io" seems to be affecting more and more people recently I've decided to study a solution that would avoid having to mess with temporary IPs and other stuff. I've found a quick and dirty workaround everyone can use in case the netplan.io package is installed.
Basically, before proceeding to purge the "cloud-init" package with APT, we can mark the package "netplan.io" as on hold in order to be sure it will not be removed; this will ensure that the "netplan.io" dependency is not touched by APT at all.
The following one-liner can be used before the
sudo apt-get purge cloud-initcommand to check if "netplan.io" is installed and put it on hold automatically:dpkg-query -W -f='${Status}' netplan.io 2>/dev/null | grep -q "install ok installed" && { sudo apt-mark hold netplan.io && echo "netplan.io put on hold"; } || echo "netplan.io is not available";More informations about apt-mark can be found in the official debian manpage: manpages.debian.org
I've also updated my Bash Script (disable-cloud-init) to include this solution.
thanks... on my sever netplan.io was removed and now I have no netplan config.. wish I knew this before :-(
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.