i recall my failed rebuild started the old container automatically
I think that happens if you run discourse-doctor.
I’m assuming you mean the docker manager here.
We do have the ability to force a CLI update via these variables – the complication here is intervention was only needed if you had one of the plugins already installed.
Perhaps it would have been a better experience for self hosters had we forced a CLI update on everyone in these sorts of cases regardless.
It all worked out in the end.
It was just a little disconcerting at first till I realized I had to go into the command line, remove plugins and rerun.
Fortunately, the end of the message on the first cli rerun indicated what had to be removed.
Oops. Right.
I think it’s a better experience if cdck errs on the side of doing a command line rebuild that will certainly work even if it might not be necessary rather than a more convenient one-click upgrade that might crash your site and require you to figure out how to do a command line rebuild.
This is a complete misunderstanding of the situation.
This change has unblocked tremendous amounts of velocity for the team. Changes that in the past would take us many hours to work through can now take us minutes.
Take adding /filter
support for assign and solved. Something I did last week. Yes, it was possible in the past but it required cross repo coordination which was very complicated to pull off, now we can do this stuff easily in 1 commit.
The end result is that the quality/stability and velocity of improvements for core plugins increases. It also gives us a better extensibility story overall cause we are less reticent to improve our extensibility story.
We did force a CLI rebuild for each batch of bundled plugins
-
bump image to discourse/base:2.0.20250710-0019 (#276) · discourse/docker_manager@5d90bc7 · GitHub
-
bump image to discourse/base:2.0.20250715-0020 (#277) · discourse/docker_manager@ec799c4 · GitHub
-
bump image to discourse/base:2.0.20250722-0020 (#280) · discourse/docker_manager@9ffff5e · GitHub
I haven’t seen any reports of failed UI rebuilds, so I think this strategy successfully pointed people to the CLI rebuild. Those CLI rebuilds then provided the ‘hint’ messages about removing lines from app.yml
.
My bad. I thought I’d seen a few, but I bet you’re paying closer attention than I am!
Sorry about that
I’m not sure how to deal with this.
Update is failing with a lot of errors similar to
HINT: The plugin ‘discourse-solved’ is now bundled with Discourse and should not be included in your container configuration.
Remove the line ‘git clone https://github.com/discourse/discourse-solved’ from your containers/web_only.yml file, then try again.
For more information, see Bundling more popular plugins with Discourse core
I edited web_only.yml and commented out all the referenced plugins, but that didn’t help.
cmd:
## - git clone
GitHub - discourse/docker_manager: Plugin for use with discourse docker image
## - git clone
GitHub - discourse/discourse-templates: A plugin that allows users to use templates to insert frequently used content
## - git clone
GitHub - discourse/discourse-akismet: give spam a whoopin
## - git clone
GitHub - discourse/discourse-chat-integration
## - git clone
GitHub - discourse/discourse-solved: Allow accepted answers on topics
## - git clone
GitHub - discourse/discourse-cakeday: Show a birthday cake emoji beside the names of members on their join anniversary, or their actual birthday -- and a browsable directory of upcoming anniversaries / birthdays.
## - git clone
GitHub - discourse/discourse-adplugin: Official Discourse Advertising Plugin. Install & Start Serving Ads on Your Discourse Forum
## - git clone
GitHub - discourse/discourse-patreon: Enable syncronization between Discourse Groups and Patreon rewards
## - git clone
GitHub - discourse/discourse-linkedin-auth: LinkedIn OAuth Login support for Discourse
## - git clone
GitHub - discourse/discourse-data-explorer: SQL Queries for admins in Discourse
## - git clone
GitHub - discourse/discourse-assign: Plugin for assigning users to a topic
## - git clone
GitHub - discourse/discourse-topic-voting: Adds the ability for voting on a topic within a specified category in Discourse.
## - git clone
GitHub - discourse/discourse-user-notes: Plugin for Staff users to create notes on users
## - git clone
GitHub - discourse/discourse-math: Official MathJax support for Discourse
## - git clone
GitHub - discourse/discourse-oauth2-basic: A basic OAuth2 plugin for use with Discourse
## - git clone
GitHub - discourse/discourse-calendar: Adds the ability to create a dynamic calendar in the first post of a topic.
## - git clone
GitHub - discourse/discourse-affiliate
## - git clone
GitHub - discourse/discourse-invite-tokens: Discourse Invite Tokens
## - git clone
GitHub - discourse/discourse-github
The hint there searches for the existence of those strings in your config, so the error text hint might be misdirecting you in this specific case.
Those lines are ok to remove (make a copy of your existing config if you are cautious) and should reveal a much more helpful error
Was this a list of what you took out, or what you still have? Because a bunch of those are in the list in the OP. Are you actually saving the yml or just exiting?
Oh I see you have a web.yml…maybe you have to do something else for that install