Continuing the discussion from Docker using a lot of CPU: [image]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 bug that exists in all versions from 17.06 to 17.11 (and, by the glacial pace at which the PR is moving, will probably be in 18.01 or whatever the next release will be). Basically, Docker’s gonna Docker, and all we can do is hang on for the ride and try and dodge the worst of the low-hanging tree branches. I had made a mental not that I’ll eventuall need to allow my instance to upgrade docker again, after downgrading because of that bug, but I’m not sure when I should do that nor how I do it without breaking stuff… Or do I need to do anything?

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!

[image] 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 performance issues between versions. Running doesn’t necessarily mean running well.

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 so I can’t say much but I never had it trigger any alerts for me. I’m however curious to know what strategy you use to observe the performance metrics for docker in relation to discourse?

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 transaction times, but as these machines only run Discourse it’s very easy to see if a docker version has an impact on load.

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: [image]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 are likely very different. That’s the “unless you have specific reasons not to” in Jeff’s post.

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 …

[image] 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.

When to upgrade docker (and how)?

Product Support

codinghorror (Jeff Atwood) August 1, 2018, 4:43am 18

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

Topic		Replies	Views
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	112285	January 16, 2025
Determining whether my VPS needs any upgrades (generally) Product Support	20	1083	March 10, 2025
Upgrade to 3.3 is failing for me Self-hosting	22	756	October 22, 2024
Old linux droplet doesn't support more recent Product Support	4	257	September 12, 2024
Docker version not supported after the later update Self-hosting	2	1274	November 4, 2017

When to upgrade docker (and how)?

Related topics