这里应该有一个错误，我尝试通过标签拉取v3.6.0.beta2，结果遇到下面的错误： FAILED -------------------- Pups::ExecError: cd /var/www/discourse && sudo -H -E -u discourse bash -c ' set -o errexit git fetch --tags --prune-tags --prune --force origin if [[ $(git symbolic-ref --short HEAD) == v3.6.0.beta2 ]] ; then git pul…

version: release/2026.1 should work fine. If you want to take advantage of the new overlapping support periods on versions, then this is the correct way to do it. (but of course, you must to remember to update manually before 2026.1 reaches its end-of-life) version: esr should also work. The system…

最后来一个总结。我们的需求是：安装指定版本更新本地代码库https://github.com/discourse/discourse_docker.git # 进入项目根目录 cd /var/discourse # 更新到最新版 git pull 修改要指定的版本修改 containers/app.yml，在最后面添加下面这个配置： params: version: release/2026.1 # 最佳实践应该写：esr 重新构建 ./launcher rebuild app 如果是version: esr则后面的都不用看了。首先 git pull，确…

[image] singi2016cn: params: version: release/2026.1 I think it would be very unusual to configure a specific version, rather than a flavour/stream/tag, like latest or stable. I’m actually no longer sure what tags are normal and available and useful with this system.

Have you taken a look at Configure a supported tracking branch to get Discourse software updates ? Maybe it helps for understanding which tags are useful

是的，普通用户使用默认的latest就足够了。但是对应我这种场景来说，不得不研究如何使用特定版本。我总不能对boss说：“哦，很遗憾，Discourse暂时不支持检出特定版本，我们只能更新到最新版。”

这个帖子非常有用，我将仔细看一下。感谢。

[image] Moin: Have you taken a look at Configure a supported tracking branch to get Discourse software updates ? I hadn’t seen that - thanks. Looks like we should be using latest/release/esr now. I see my own (old) app.yml picks up the default by being commented out: ## Which Git revisio…

version 目前不支持标签，如果要支持，需要修改构建的脚本。本来最佳实践是： params: version: esr 但是目前，不得不修改成 params: version: release/2026.1

Interesting. Even before the new versioning strategy, beta had been a tag instead of a branch for quite a while: Upcoming changes to the beta branch of Discourse

是我，我也很困惑，但是目前的构建代码确实无法使用标签。这本不应该如此。

Something doesn’t appear to be right here. I was running v3.5.0 beta3 with the yml set to version: tests-passed Then I noticed this versioning change so before rebuilding I changed the yml to version: esr and then did a rebuild from the CLI. Now in discourse I see Installed 2026.3.0-latest.1 T…

Help deploying older versions of Discourse

Support Self-hosting

Ed_S (Ed S) March 28, 2026, 8:07pm 21

I believe version should be indented because it’s part of params.

Topic		Replies	Views
How can i rebuild discourse without changing version? Self-hosting	11	2676	February 5, 2021
Unable to make the version of `2.9.0.beta6` running Self-hosting unsupported-install	5	358	April 16, 2024
Shallow git fetch regression in discourse_docker Support	16	2359	February 5, 2021
Stable branch compatibility with discourse_docker and plugins Self-hosting stable	39	2577	February 3, 2024
Trouble upgrading from 3.3.0.beta1 to 3.3.0.beta6 Self-hosting	22	321	August 8, 2024

Help deploying older versions of Discourse

Related topics