# Discourse Update/Upgrade afhankelijkheidscontrole

**URL:** https://meta.discourse.org/t/discourse-update-upgrade-dependency-check/368142
**Category:** Feature
**Created:** [29 mei 2025 om 19:53 UTC](https://meta.discourse.org/t/discourse-update-upgrade-dependency-check/368142 "2025-05-29T19:53:13Z")
**Posts on this page:** 1
**Showing post:** 6

<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: [29 mei 2025 om 23:29 UTC](https://meta.discourse.org/t/discourse-update-upgrade-dependency-check/368142/6 "2025-05-29T23:29:23Z")

</div>

> [@Heliosurge](#):
>
> Most ppl install an OS and generally keep it upto date

Not the people I work with. They won’t update it when I tell them it’s behind eol.

> [@Heliosurge](#):
>
> If the Updating in the web identified the Docker version was not minimum

I’m pretty sure that stuff running inside the container cannot tell what version of docker it’s running under.

Maybe it can. It looks like you can get this from inside a container to see what version is running.

`https://docs.docker.com/engine/api/v1.30/#operation/SystemVersion`

So maybe they could do better. That could be a cool thing to add to the dashboard,if it really does work.

> [@Heliosurge](#):
>
> I tried ./launcher start app
> 
> Which failed.

It usually works. An exception is if the database has been migrated.

If the os is out of date I generally find it easier and safer to move to a new vm. Ideally you do it whilst the old server still works. See [Move a Discourse site to another VPS with rsync](https://meta.discourse.org/t/move-a-discourse-site-to-another-vps-with-rsync/43812)

If you have a backup, you can skip copying the database and skip the database upgrade, just restore it on the new database.

---

_[View the full topic](https://meta.discourse.org/t/discourse-update-upgrade-dependency-check/368142)._