# Failed web Discourse upgrade. Web docker upgrade worked
**URL:** https://meta.discourse.org/t/failed-web-discourse-upgrade-web-docker-upgrade-worked/350613
**Category:** Self-hosting
**Created:** [February 5, 2025, 12:33pm UTC](https://meta.discourse.org/t/failed-web-discourse-upgrade-web-docker-upgrade-worked/350613 "2025-02-05T12:33:40Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@GetReadyMan](https://meta.discourse.org/u/GetReadyMan)
#### Post date: [February 5, 2025, 12:33pm UTC](https://meta.discourse.org/t/failed-web-discourse-upgrade-web-docker-upgrade-worked/350613/1 "2025-02-05T12:33:40Z")
The web version of the Docker update worked, The web version of the Discourse update failed.
I reset the failed update, but the web application said the update was in progress.
Went to try to update Discourse manually
cd /var/discourse
./launcher rebuild app
Got the following error.
ERROR: Docker version 19.03.13 not supported,please upgrade to at least 20.10.0, or recommend 24.0.7
I tried to upgrade the Docker manually:
wget -qO- [https://get.docker.com/](https://get.docker.com/) | sh
and got the following error:
E: Could not get lock /var/lib/dpkg/lock-frontend. It is being held by process 10528 (apt-get)
E: Unable to aquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
My discourse website is down with an _Oops-Error 500_
Any thoughts?
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [February 5, 2025, 1:09pm UTC](https://meta.discourse.org/t/failed-web-discourse-upgrade-web-docker-upgrade-worked/350613/2 "2025-02-05T13:09:07Z")
There are a few topics about this docker version error:
> [@Issue After Docker Update: Unsupported Version Error](https://meta.discourse.org/t/issue-after-docker-update-unsupported-version-error/344700/3):
>
> Thank you. The command you provided did not work. I resolved it with the following solution from ChatGPT: To update Docker on a DigitalOcean Droplet, follow these steps: 1. Check the Current Version of Docker Run this command to see the currently installed Docker version: docker --version 2. Update the Operating System Make sure the operating system is up-to-date: sudo apt update && sudo apt upgrade -y 3. Uninstall the Old Version of Docker (if necessary) Remove any existing version of Doc…
> [@Admin/Update screen is blank. How to manually updtate docker via SSH Console?](https://meta.discourse.org/t/admin-update-screen-is-blank-how-to-manually-updtate-docker-via-ssh-console/347318/3):
>
> There’s a good chance your OS is out of date and that you should move to a fresh new VM. Does cat /etc/issue suggest that you have 18.04? You can try apt update;apt install docker-ce Another way, that prints a scary message, but is probably safe if you installed docker with apt wget -qO- https://get.docker.com/ | sh
---
### Author:  [@GetReadyMan](https://meta.discourse.org/u/GetReadyMan)
#### Post date: [February 5, 2025, 1:34pm UTC](https://meta.discourse.org/t/failed-web-discourse-upgrade-web-docker-upgrade-worked/350613/3 "2025-02-05T13:34:20Z")
Coin, Thanks for the pointers to the topics!
I get the Docker version as 19.03.13. I then go to update the opertaing system with
_sudo apt update && sudo apt upgrade -y 3_
and the update gets stuck at…
_Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 10528 (apt-get)… 454s_
with the number of seconds increasing.
---
### Author:  [@GetReadyMan](https://meta.discourse.org/u/GetReadyMan)
#### Post date: [February 5, 2025, 6:47pm UTC](https://meta.discourse.org/t/failed-web-discourse-upgrade-web-docker-upgrade-worked/350613/4 "2025-02-05T18:47:24Z")
Here’s the fix from ChatGPT. The key was to force kill the stuck process in step 3.
The error indicates that another `apt` or package management process is already running and holding the lock file `/var/lib/dpkg/lock-frontend`. This situation prevents your `apt` command from proceeding. Here’s how to resolve the issue:
### Steps to Fix the Issue
1. **Check for Running `apt` Processes**
Run the following command to check for other `apt` processes:
2. **Wait for the Process to Finish**
If another process is genuinely running, it’s best to wait for it to complete. Sometimes, unattended upgrades or package installations run in the background.
3. **Force Kill the Stuck Process**
If the process has been running for an abnormally long time, you can terminate it:
4. **Remove Lock Files**
After killing the process, remove the lock files to ensure no stale locks exist:
5. **Reconfigure the Package Database**
Run this command to fix any potential issues with the package manager:
6. **Retry the Update**
Now, retry your update command:
### Notes
- If this issue occurs frequently, check if unattended upgrades or automated updates are running in the background. These can cause conflicts when manually managing packages.
- To disable unattended upgrades, you can run:
```bash
sudo systemctl disable --now unattended-upgrades
```
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [March 7, 2025, 6:48pm UTC](https://meta.discourse.org/t/failed-web-discourse-upgrade-web-docker-upgrade-worked/350613/5 "2025-03-07T18:48:22Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.