# Any risk of upgrading Ubuntu 17.10 --\> 18.04.1 LTS

**URL:** https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922
**Category:** Support
**Created:** [September 24, 2018, 9:43am UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922 "2018-09-24T09:43:35Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![frold](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frold/32/82547_2.png) [@frold](https://meta.discourse.org/u/frold)
#### Post date: [September 24, 2018, 9:43am UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922/1 "2018-09-24T09:43:35Z")

</div>

Im running at Ubuntu 17.10. When I log into my terminal it says

> New release ‘18.04.1 LTS’ available.  
> Run ‘do-release-upgrade’ to upgrade to it.

Is it safe to do? Will it break my docker and discourse?..

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 24, 2018, 10:10am UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922/2 "2018-09-24T10:10:26Z")

</div>

It’ll probably work. In my opinion it’s easier to install the new os and start fresh, but I’ve seen reports of upgrades wiring just fine.

In any case, make sure that you have a backup of Discourse and your app.yml. That’s all you need to restore discourse.

---

<div class="post-metadata">

### Author: ![dnsmichi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dnsmichi/32/379505_2.png) [@dnsmichi](https://meta.discourse.org/u/dnsmichi)
#### Post date: [September 24, 2018, 11:23am UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922/3 "2018-09-24T11:23:39Z")

</div>

If you’re using Docker from a separate repository, the upgrade mechanism might disable it and you need to later update/re-enable it to get to most recent Docker package to run Discourse.

I generally stick to LTS versions, on 16.04 I’ll get that every time I login. I would suggest an upgrade from 17.10 though, since the LTS versions have proven to be supported long term running stable. `do-release-upgrade` works fine, even from LTS to LTS.

Once there’s 20.04 LTS, stick with 18.04 for a while until at least the first point release is out.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 14, 2018, 5:16pm UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922/4 "2018-10-14T17:16:52Z")

</div>

I just performed `do-release-upgrade` on one of my Production servers with no issues (apart from having to install the following packages in order to have that command available):

```plaintext
sudo apt-get install update-manager update-manager-core

```

I was upgrading from 16.04.

The server restarted and my Discourse instance appeared no problem.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [October 14, 2018, 10:01pm UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922/5 "2018-10-14T22:01:55Z")

</div>

If it’s not a critical server it’s usually fine to do.

If uptime matters to you it’s always better to deploy a fresh box at the new software level and migrate your configuration. In the event something goes awry you will have an option to back out of the upgrade without losing data. Providing you’re using something like DO you won’t have two servers running in parallel for too long.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [October 14, 2018, 10:31pm UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922/6 "2018-10-14T22:31:02Z")

</div>

You can also use an elastic ip (I think that’s what they call it) to switch over to the new server without waiting for dns to propagate.

- Assign the elastic ip to the old server
- Point dns to the elastic ip
- set up new server
- freeze old site and take backup
- restore backup to new server
- assign ip to new server

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [October 15, 2018, 12:40am UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922/7 "2018-10-15T00:40:41Z")

</div>

You’re not supposed to use non-LTS distributions with Discourse anyway – we don’t recommend it.

Upgrading from one LTS release to another LTS release is safe, and has been done many times.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [July 6, 2021, 3:07pm UTC](https://meta.discourse.org/t/any-risk-of-upgrading-ubuntu-17-10-18-04-1-lts/97922/8 "2021-07-06T15:07:20Z")

</div>


