# Discourse\_docker not forcing command line upgrade?
**URL:** https://meta.discourse.org/t/discourse-docker-not-forcing-command-line-upgrade/224426
**Category:** Self-hosting
**Created:** [April 15, 2022, 3:01pm UTC](https://meta.discourse.org/t/discourse-docker-not-forcing-command-line-upgrade/224426 "2022-04-15T15:01:08Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 15, 2022, 3:01pm UTC](https://meta.discourse.org/t/discourse-docker-not-forcing-command-line-upgrade/224426/1 "2022-04-15T15:01:08Z")
It seems that this is a security issue that requires a command-line upgrade, but I’m seeing a forced rebuild on only a couple of the sites that I’ve checked, and those seem really old.
Continuing the discussion from [2.9.0.beta4: Security Fixes, Sitemaps, Discourse Connect Provider 2FA, and more](https://meta.discourse.org/t/2-9-0-beta4-security-fixes-sitemaps-discourse-connect-provider-2fa-and-more/224271):
> [@2.9.0.beta4: Security Fixes, Sitemaps, Discourse Connect Provider 2FA, and more](https://meta.discourse.org/t/2-9-0-beta4-security-fixes-sitemaps-discourse-connect-provider-2fa-and-more/224271/1):
>
> **Rebuild required.** The rebuild will update package versions to latest, and must be completed if the site has not be been rebuilt from the command line in the past day.
I’ve checked a bunch of sites today and none of them has the “You have to do a command line upgrade” message on the upgrade page.
Is this a bug?
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [April 15, 2022, 3:09pm UTC](https://meta.discourse.org/t/discourse-docker-not-forcing-command-line-upgrade/224426/2 "2022-04-15T15:09:55Z")
You have to update docker\_manager first in order to see it. After you update the docker\_manager, the next request to `/admin/upgrade` will show the message.
---
### Author:  [@geoff777](https://meta.discourse.org/u/geoff777)
#### Post date: [April 15, 2022, 3:12pm UTC](https://meta.discourse.org/t/discourse-docker-not-forcing-command-line-upgrade/224426/3 "2022-04-15T15:12:18Z")
I updated an instance today from the console.
I expected to see a message but didn’t get one.
I did a `./launcher rebuild app` just to be safe …
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 15, 2022, 3:42pm UTC](https://meta.discourse.org/t/discourse-docker-not-forcing-command-line-upgrade/224426/4 "2022-04-15T15:42:24Z")
Darn. Ok. I guess the old one can’t know that until the upgrade.
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [April 15, 2022, 4:38pm UTC](https://meta.discourse.org/t/discourse-docker-not-forcing-command-line-upgrade/224426/5 "2022-04-15T16:38:11Z")
> [@Falco](#):
>
> You have to update docker\_manager first in order to see it. After you update the docker\_manager, the next request to `/admin/upgrade` will show the message.
This might explain something I saw: I did the docker update, navigated successfully back to the versions tab and then did the discourse update. All in browser and all apparently successful. But opening a new processes tab in another window showed me the static page telling me I needed to rebuild.
In a sense, I didn’t need to - and I haven’t. My discourse thinks it is fully updated. Is it? If it isn’t, what state is it in?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [May 15, 2022, 4:39pm UTC](https://meta.discourse.org/t/discourse-docker-not-forcing-command-line-upgrade/224426/6 "2022-05-15T16:39:02Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.