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!

Upgraded Ubuntu and Docker, but now my site says “The site can’t be reached.” Not sure what the next step in the troubleshooting process ought to be; attempting to check out docker logs now. This means nothing to me, but maybe it means something to one of you: [Screenshot 2025-02-10 at 2.50.57 PM] Aaaand now it’s a 502 error.

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.

[图片] Jay Pfaffman: You can search for that error and get some ideas. This is what I have been doing, both in this forum and beyond. [图片] Jay Pfaffman: If you don’t want to upgrade your OS, you don’t want to upgrade Discourse. 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

[图片] pearsonified: /etc/apt/sources.list 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?

Here are the last few lines of that file. Readout says “Read 59 lines,” so is line 58 the last one or the one before it? Neither line looks messed up to me, so I’m not sure what to delete… [Screenshot 2025-02-10 at 1.46.28 PM]

尝试在 DigitalOcean 上更新 Docker；卡在 Docker 19.03.13 😔

产品支持

pfaffman (Jay Pfaffman) 2025 年2 月 10 日 19:41 6

抱歉。我的建议是启动一个新的、可用的且已升级的服务器。这是万无一失、更快、更安全的方法。请参阅使用 rsync 将 Discourse 站点迁移到另一台 VPS。

话题		回复	浏览量
Issue After Docker Update: Unsupported Version Error Product Support	3	768	2024 年12 月 29 日
Failed web Discourse upgrade. Web docker upgrade worked Self-hosting	3	256	2025 年2 月 5 日
Upgrade failed because Docker out of date Self-hosting	5	1758	2015 年7 月 5 日
Update broken stuck on Docker version Product Support	9	577	2025 年2 月 14 日
"ignoring file '50unattended-upgrades.wcf-dist' in directory '/etc/apt/apt.conmf.d/' as it has an invalid filename extension Self-hosting	18	3737	2017 年2 月 20 日

尝试在 DigitalOcean 上更新 Docker；卡在 Docker 19.03.13 😔

相关话题