Continuing the discussion from Docker using a lot of CPU : [画像] Docker using a lot of CPU > Looks like one should be rather conservative in upgrading docker? Being conservative in upgrading docker isn’t even enough; we follow that policy (still on 17.06), and we still got hit by a ripper of a bu…

We’re on version 18.04.0-ce, build 3d479c0 across at least 5 known good instances. Haven’t had any issues due to docker yet!

[画像] itsbhanusharma: Haven’t had any issues due to docker yet! Pretty much a guaranteed way to jinx your installs! Seriously though, over the past few years we’ve had a number of run-ins with docker versions. Even if instances appear to be building and running ok there have been plenty of pe…

I’d totally agree to that, There have been multiple edge cases and other complaints due to people being on a specific version of docker which contains some bug. About the performance part, I haven’t really invested myself into creating stats for known good and the delta between those and the latest …

Usually the difference is observable from whatever server management you use, we’ve got everything in either AWS or DO and most of it is hooked up into New Relic. If there’s a performance difference there’s also usually an observable step up or down in CPU usage. We’ve not gone so far as to look at…

I would use latest Docker unless you have specific reasons not to.

Well, @mpalmer seemed to think differently, and he seemed to suggest that that is not what you’re doing: [画像] Docker using a lot of CPU we follow that policy (still on 17.06) But okay. So my question then is: is there still a reason not to use the latest version?

I provide insights into our environment, processes, and decision-making for informational purposes only, unless clearly stated otherwise. What we at CDCK do, given our scale, priorities, and the skills and experience of our team, is not necessarily a good idea for everyone else, whose circumstances…

Yes, I understand. I was just wondering whether such reasons currently exist.

I’d interpret that as “specific reasons that your installation of Discourse is different from ‘Most’ installations of Discourse”. Or “you should already know if this applies to you” or “your sysadmin said you need to hold back the upgrade” or …

[画像] riking: your sysadmin said you need to hold back the upgrade Well, something like that happened back then . But I guess the reasons for being more than conservative with docker upgrades that existed some months ago don’t exist anymore. Otherwise we’d have heard them by now.

Docker のアップグレード時期と方法（いつ、どうやって？）

サポート

codinghorror (Jeff Atwood) 2018 年 8 月 1 日午前 4:43 18

It is quite safe since the container file is not touched.

トピック		返信	表示
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	111390	2025 年 1 月 16 日
Determining whether my VPS needs any upgrades (generally) Support	20	911	2025 年 3 月 10 日
Upgrade to 3.3 is failing for me Self-hosting	22	639	2024 年 10 月 22 日
Old linux droplet doesn't support more recent Support	4	233	2024 年 9 月 12 日
Docker version not supported after the later update Self-hosting	2	1223	2017 年 11 月 4 日

Docker のアップグレード時期と方法（いつ、どうやって？）

関連トピック