# How to update to latest 2.x instead of 3.0?

**URL:** <https://meta.discourse.org/t/how-to-update-to-latest-2-x-instead-of-3-0/252318>\
**Category:** Self-hosting\
**Created:** [January 19, 2023, 5:10pm UTC](https://meta.discourse.org/t/how-to-update-to-latest-2-x-instead-of-3-0/252318 "2023-01-19T17:10:44Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [January 19, 2023, 9:41pm UTC](https://meta.discourse.org/t/how-to-update-to-latest-2-x-instead-of-3-0/252318/4 "2023-01-19T21:41:14Z")

</div>

> [@jonom](#):
>
> I thought given the major version bump I would hold off on updating in case of any breaking changes

Discourse does not follow the SemVer spec. Every 2.X release was also a major release.

> [@jonom](#):
>
> I guess since Discourse runs in a Docker container, if my server (Ubuntu 18) can run Discourse v2 it should be able to run Discourse v3?

We ship the Discourse Docker image, and we ensure it’s compatible with both the default release channel (Discourse 3.1 at the moment) and the stable release channel (Discourse 3.0 at the moment). This image isn’t compatible with Discourse 2.x anymore, and pinning to an old image is not recommended as it contains EOL software in it.

---

_[View the full topic](https://meta.discourse.org/t/how-to-update-to-latest-2-x-instead-of-3-0/252318)._