Ubuntu wiki<\/a>.<\/p>\nWe do<\/em> have a workaround, however. You can use the -d<\/code> option to upgrade to a development release.<\/p>\n$ sudo do-release-upgrade -d\n\nChecking for a new Ubuntu release\nGet:1 Upgrade tool signature [819 B] \nGet:2 Upgrade tool [1,257 kB] \nFetched 1,258 kB in 0s (0 B\/s) \nauthenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' \nextracting 'bionic.tar.gz'\n\nReading cache\n\nChecking package manager\n\nContinue running under SSH? \n\nThis session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover. \n\nIf you continue, an additional ssh daemon will be started at port \n'1022'. \nDo you want to continue? \n\nContinue [yN] y\n<\/code><\/pre>\nSince you\u2019re using an SSH connection to start the upgrade process, the system asks whether you want to upgrade through SSH this connection. Press y<\/code> to continue.<\/p>\nStarting additional sshd \n\nTo make recovery in case of failure easier, an additional sshd will \nbe started on port '1022'. If anything goes wrong with the running \nssh you can still connect to the additional one. \nIf you run a firewall, you may need to temporarily open this port. As \nthis is potentially dangerous it's not done automatically. You can \nopen the port with e.g.: \n'iptables -I INPUT -p tcp --dport 1022 -j ACCEPT'\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n........\n........ \nFetched 0 B in 0s (0 B\/s) \nReading package lists... Done \nBuilding dependency tree \nReading state information... Done\n\nUpdating repository information\n\nNo valid mirror found \n\nWhile scanning your repository information no mirror entry for the \nupgrade was found. This can happen if you run an internal mirror or \nif the mirror information is out of date. \n\nDo you want to rewrite your 'sources.list' file anyway? If you choose \n'Yes' here it will update all 'xenial' to 'bionic' entries. \nIf you select 'No' the upgrade will cancel. \n\nContinue [yN]y\n<\/code><\/pre>\nThe update manager informs you that a new SSH process is now running on port number 1022. You can add this port number to your firewall rules, if you have them, to allow this SSH connection as a precautionary measure. If for some reason the SSH connection drops and cannot let you connect again via port 22, you can connect to this new SSH instance using port 1022.<\/p>\n
Press y<\/code> to continue:<\/p>\n..............\n..............\nChecking package manager\nReading package lists... Done \nBuilding dependency tree \nReading state information... Done\n\nCalculating the changes\n\nCalculating the changes\n\nDo you want to start the upgrade? \n\n3 installed packages are no longer supported by Canonical. You can \nstill get support from the community. \n\n88 new packages are going to be installed. 333 packages are going to \nbe upgraded. \n\nYou have to download a total of 230 M. This download will take about \n56 seconds with your connection. \n\nInstalling the upgrade can take several hours. Once the download has finished, the process cannot be canceled.\n\nContinue [yN] Details [d]y\n<\/code><\/pre>\nOnce again, press y<\/code> to continue. The update manager now starts downloading new packages for the upgrade and will inform you about the time remaining. New packages are be downloaded, unpacked, and installed one by one in your system. During the procedure, you will be asked to choose your keyboard- configuration, and if you want to restart services automatically when required.<\/p>\nGenerally speaking, it is safe to restart these services. You may also be prompted to replace the configuration files for a service you may have configured earlier.<\/p>\n
Searching for obsolete software\nReading package lists... Done \nBuilding dependency tree... 50%\nBuilding dependency tree \nReading state information... Done\nReading state information... Done\n\nRemove obsolete packages? \n\n36 packages are going to be removed. \n\nContinue [yN] Details [d]y\nSystem upgrade is complete.\n<\/code><\/pre>\nNext, the update manager asks you to remove obsolete packages. It is safe to answer y<\/code> in a system where you have not modified the packages extensively. In a system where you have modified the packages heavily, you probably want to check in details (the d<\/code> option).<\/p>\nAt this stage, the upgrade is finished.<\/p>\n
Restart required \n\nTo finish the upgrade, a restart is required. \nIf you select 'y' the system will be restarted. \n\nContinue [yN]y\n<\/code><\/pre>\nPress y<\/code> to do a restart of your system.<\/p>\nIf everything goes well, the system will be restarted. Login to the upgraded system, you will be greeted by a welcome prompt:<\/p>\n
Welcome to Ubuntu 18.04 LTS <\/code><\/pre>\n![\"\"](\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2018\/05\/201805_1804-celebrate.gif\")
<\/p>\n
You can also check the release version in the terminal, as you did at the beginning of this tutorial:<\/p>\n
$ cat \/etc\/lsb-release \nDISTRIB_ID=Ubuntu\nDISTRIB_RELEASE=18.04\nDISTRIB_CODENAME=bionic\nDISTRIB_DESCRIPTION=\"Ubuntu 18.04 LTS\"\n<\/code><\/pre>\nNow that your system is upgraded to latest release which is Ubuntu 18-04 Bionic Beaver, you can test the new versions of your software and services against the previous ones. Make sure everything works as expected, and have fun on the new Ubuntu LTS!<\/p>\n","protected":false},"excerpt":{"rendered":"
Upgrade to Ubuntu 18.04 from 16.04 on your VPS with a few simple commands and a short wait, and then take advantage of all the new features on your virtual private server (VPS)!<\/p>\n","protected":false},"author":20,"featured_media":2934,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[18,30],"tags":[185],"class_list":["post-1921","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","category-tutorials","tag-ubuntu"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/posts\/1921","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/comments?post=1921"}],"version-history":[{"count":2,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/posts\/1921\/revisions"}],"predecessor-version":[{"id":13066,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/posts\/1921\/revisions\/13066"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/media\/2934"}],"wp:attachment":[{"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/media?parent=1921"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/categories?post=1921"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/tags?post=1921"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}