On one of my self-hosted Discourse, (fully up to date docker_manager and a docker image only a few weeks old ) I just ran in this error upgrading. I don’t know what version the site was on before, but it was only about 30 commits behind on tests-passed. https://gist.github.com/YesThatAllen/359c8e6a4687ca4b0186 The site seems to be fine & responding, but I figured I’d mention something before I ./launcher rebuild app PS no, this isn’t the site I mess with server.en.yml, it’s just plain Discourse

[image] watchmanmonitor: I don’t see any notice that my container is out of date You won’t see one at the moment because the BUNDLED WITH in the Gemfile.lock got missing again (cc @eviltrout) :wink: [image] watchmanmonitor: or if it even matters No, it doesn’t matter when you are using the Docker container. It’s just an annoyance during development when there’s a version mismatch, but you can completely ignore it in production. So, there’s no need to worry about Bundler when you click on Upgrade.

This means you need to log in via SSH and do the classic 3-liner git pull , etc, to update the container.

ok, I didn’t see a notice in admin warning that my docker image was out of date, so I didn’t consider checking it. # cd /var/discourse # git pull remote: Counting objects: 4, done. remote: Total 4 (delta 2), reused 2 (delta 2), pack-reused 2 Unpacking objects: 100% (4/4), done. From https://github.com/discourse/discourse_docker 9e83982..904f795 master -> origin/master Updating 9e83982..904f795 Fast-forward launcher | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) root@discuss:/var/discourse# ./launcher rebuild app And, all seems to be well now.

So now I get this on another discourse I host.. $ cd /var/www/discourse && git fetch && git reset --hard HEAD@{upstream} HEAD is now at fc090b4 FIX: With many stickies some latest posts got missed ******************************************************** *** Please be patient, next steps might take a while *** ******************************************************** $ bundle install --deployment --without test --without development Warning: the running version of Bundler is older than the version that created the lockfile. We suggest you upgrade to the latest version of Bundler by running `gem install bundler`. Warning: the running version of Bundler is older than the version that created the lockfile. We suggest you upgrade to the latest version of Bundler by running `gem install bundler`. How can be warned ahead of time that we need to update the container? And, do we always need to rebuild after updating the container?

Rebuild their the container it will update bundler

I was 96 commits behind in a self-hosted forum, and just updated. I got this bundler version warning again.. how can we warned ahead of time if our container is out of date? (Didn’t we used to get this notice?)

Are you sure the container is out of date or if it’s Bundler having added “BUNDLED WITH” to the lock file? I can’t find the discussion now, but AFAIK this was causing grief and it no longer does this. CHANGELOG.md master ## 2.1.4 (January 5, 2020) Bugfixes: - Fix `net-http-pipeline` no longer being allowed in Gemfiles if already installed in the system due to our vendored version of `net-http-persistent` optionally requiring it [#7529](https://github.com/bundler/bundler/pull/7529) - Fix inline gems no longer being requirable if no Gemfile is present in the directory hierarchy [#7537](https://github.com/bundler/bundler/pull/7537) ## 2.1.3 (January 2, 2020) Bugfixes: - Fix `rake build` when path has spaces on it [#7514](https://github.com/bundler/bundler/pull/7514) - Fix `rake release` git push tasks when the running shell has `git` as an alias of another command (like `hub`) [#7510](https://github.com/bundler/bundler/pull/7510) - Fix some circular require warnings [#7520](https://github.com/bundler/bundler/pull/7520) - Fix `bundle config set deployment true` recommended alternative to `bundle config --deployment` to behave in the same way as the `--deployment` flag [#7519](https://github.com/bundler/bundler/pull/7519) ## 2.1.2 (December 20, 2019) Bugfixes: This file has been truncated. show original

Pretty sure bundler is out of date: From may last one-click update: $ bundle install --deployment --without test --without development Warning: the running version of Bundler is older than the version that created the lockfile. We suggest you upgrade to the latest version of Bundler by running gem install bundler. But even if it’s just bundler being annoying.. I bet this is something the discourse team can make less confusing.

[image] Mittineague: Are you sure the container is out of date or if it’s Bundler having added “BUNDLED WITH” to the lock file? On my other two hosts where I did [image] codinghorror: do the classic 3-liner: cd /var/discourse git pull ./launcher rebuild app update the container. Bundler must have been updated, because the issue goes away.

One of my communities is 189 commits behind at the moment, I don’t see any notice that my container is out of date, but I don’t have any confidence that that bundler in use matches what’s current, or if it even matters. Currently, I won’t know until I hit Upgrade, and get a warning. Then if I do, I’ll have to re-upgrade at the command line. How are we supposed to predict what’s going to happen when I click Upgrade?

Bundler version warning while updating

Product Support

codinghorror (Jeff Atwood) July 4, 2015, 11:22pm 10

Correct, updating from the command line will update the docker image, etc.

Topic		Replies	Views
No longer getting notifications for out of date containers Product Support	6	2646	May 18, 2019
Bundler version Product Support docker	4	1751	June 9, 2015
Bundler is older - message Product Support	1	628	October 20, 2016
Updating and container rebuild fails Self-hosting	0	464	February 26, 2021
Can't get Ruby to update so ./launcher rebuild app keeps failing Self-hosting	15	910	May 22, 2024

Bundler version warning while updating

Related topics