Droplet upgrading 14.04 -> 15.10 -> 16.04 -> 16.10 -> 17.04 etc?

Although I’ve successfullying upgraded the same Ubuntu droplet in the past two years and just got 16.04 working, I needed to get support to reset the networking.

That gave rise to some comments to the advantages/disadvantages of a kernel provided by the “do-release-upgrade” (term used was a hypervisor managed kernel) and those provided by DigitalOcean via the control panel (term used was a managed kernel).

I don’t understand! Please can someone explain.

Am I unusual in having used “do-release-upgrade”?

Do most clients of DigitalOcean use the kernel provided when the droplet is created and only keep the security updated. Then create a new droplet when a new Ubuntu version is released and migrate all programs and data over?

Thanks John


Submit an 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.

There are probably some advantages/disadvantages to either way; however, sticking with LTS (12.04, 14.04, 16.04…) is a good start, since they each have 5 years of support.

for my servers, I prefer to stick with an LTS for most of its life, and just start with a clean slate when it is time to upgrade. This sort of forces me to think through what I am using/not using, and clean up scripts, old user accounts, ssh keys, etc.

Having said that…I have been running the same install of Ubuntu on my desktop now for many years because I have been too lazy to wipe it clean, and I just keep upgrading to the next release…