Question
Why "cloud-init" is kept back in a new droplet with Ubuntu 16.04 while doing an "apt upgrade"?
- Posted on July 11, 2017
- Linux BasicsUbuntu 16.04
Asked by ricardoe56cf7fd
I have checked with “apt-mark hold cloud-init” and got the following mesage: “cloud-init was already set on hold.”
Is it safe to unhold it and upgrade it?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Thank you for the answers.
There is another method to update it, wich is:
in the first place to unhold the holded package, and then
My questions are:
I would not recomend apt dist-upgrade as it involves updating other staff from vesion to version.
Straight from DO support: “We pin cloud-init to a specified version in order to prevent upgrades from affecting the configuration options within your Droplet. While upgrades to cloud-init should not affect your Droplet, there have been certain situations where changes to the system had been performed due to cloud-init upgrades.”
Based on that, I would say that it “should” be safe to unpin and upgrade it, but why take the chance?
I had the same problem and it seems like a strange situation to me. Anyway, I fixed this by installing the
cloud-initpackage:sudo apt install cloud-init.