pearsonified is struggling to update Docker from version 19.03.13 to 20.10.0 or 24.0.7 on a DigitalOcean Droplet running Discourse. Attempts to follow existing guides, including Jayās solution, fail due to a persistent āmalformed entry 58ā error in /etc/apt/sources.list, which blocks apt update. pfaffman advises upgrading the OS or, preferably, migrating to a fresh server using rsync, warning that in-place upgrades are risky and time-consuming. Jagster suggests manually editing sources.list to remove the problematic line, noting that DOās backports may be involved but are likely harmless. pearsonified asks if DOās snapshot feature could help, but Jagster confirms it creates an exact copy, including the broken config. After removing the offending line, pearsonified successfully upgrades Ubuntu and Docker, but the site becomes unreachable (āThe site canāt be reachedā ā 502 error). Running launcher rebuild restores the site pearsonified. pfaffman congratulates them and marks the upgrade as the solution, noting the rebuild was the final necessary step. The thread highlights the fragility of in-place upgrades on aging systems and the efficiency of migration over repair.
Iāve tried following other (closed) threads on here re: updating Docker, but every approach Iāve tried fails for one reason or another.
Like many others here, Iām running Discourse on a DigitalOcean Droplet. But I am unable to update to 20.10.0 (or, ideally, 24.0.7).
Just hoping to find some direction so I can update Docker from the command prompt. Thank you!
More context: When I try Jayās solution, I receive the following errors:
E: Malformed entry 58 in list file /etc/apt/sources.list (URI parse)
E: The list of sources could not be read.
Curiously, this error repeats 3 times. (Perhaps because Iāve tried to do this too many times and have installed multiple flawed versions of the same thing? If so, Iāve no idea how to clean that upā¦)
This is looking more and more like I need to update Ubuntu, but I am having trouble with that as well.
If I type apt update, I still receive the malformed entry 58 error.
You can search for that error and get some ideas.
Your OS is out of date. Your sources.list is out of date. You need to upgrade your server. I would recommend that you move to a new one.
Itās possible that you have a new OS (but thatās unlikely since thatās a very old Docker, circa 2021) and that somehow something messed up that file.
If you donāt want to upgrade your OS, you donāt want to upgrade Discourse.
This is what I have been doing, both in this forum and beyond.
I am happy to do this, but I am running into an issue with the malformed entry 58 error. Could the issue be that my server is not running https and the sources.list file only has http references?
If I can get past this step, I can upgrade the OS. Problem is, I donāt know how to get past where Iām at now.
Sorry. My recommendation is that you spin up a new server that works and is already upgraded. Itās foolproof, faster, and safer. See Move a Discourse site to another VPS with rsync
nano /etc/apt/sources.list and remove that line. You, or some script has added bad line there.
I may end up doing thisāeven though it sounds like it will chew up a couple of daysābut I struggle to believe that itās simpler than just updating Ubuntu on this Droplet.
With all the people here running Discourse on Droplets, thereās no known way to get over this hurdle?
It will chew up fewer days than trying to run dist upgrade
Can I use DOās āCreate from Snapshotā functionality? Or will that just put the same, tired OS on my new Droplet?
Donāt struggle 
Iāve done both. Timewise starting new one is faster, but you must add ssh keys to get rsync working. It takes few minutes, if youā e never done it before ā but it is easy.
Upgrading Ubuntu takes longer, because you must take snapshot before. After that there is plenty of questions, mostly about configurations, and those takes some times too to make your mind (use old ones is my advise if you take that road). But you canāt totally sure if something old is left behind.
I would wonder what those backports are. Comment those last lines and try. Because you have done snapshot all you loose is time.
The only time upgrading of Ubuntu didnāt work for me happened on DO, though.
edit
I checked my VPS in DO, and it has those backports too. So those must be some custom from DO.
No, you canāt. It creates 1:1 copy.
Ok, that was NOT the end of the file, and I removed the line that got added while I was fiddling with the installation. Gonna try some of these tutorials again.
Ran the launcher rebuild again, and the forums are back up 
Thatās awesome! Congrats! Glad you got it fixed!
I marked your āupgradedā post as the solution. That was the real fix, even though you needed to do one more rebuild.
