### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [June 20, 2015, 6:08am UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/1 "2015-06-20T06:08:16Z")
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.
>
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
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 20, 2015, 6:12am UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/2 "2015-06-20T06:12:09Z")
This means you need to log in via SSH and do the classic 3-liner `git pull` , etc, to update the container.
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [June 20, 2015, 6:23am UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/3 "2015-06-20T06:23:31Z")
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.
```plaintext
# 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.
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [June 25, 2015, 9:35pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/4 "2015-06-25T21:35:13Z")
So now I get this on another discourse I host..
```plaintext
$ 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?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 25, 2015, 9:43pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/5 "2015-06-25T21:43:29Z")
Rebuild their the container it will update bundler
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [July 4, 2015, 5:08pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/6 "2015-07-04T17:08:30Z")
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?)
---
### Author:  [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [July 4, 2015, 5:34pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/7 "2015-07-04T17:34:17Z")
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.
>
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [July 4, 2015, 5:40pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/8 "2015-07-04T17:40:50Z")
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.
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [July 4, 2015, 11:20pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/9 "2015-07-04T23:20:42Z")
> [@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
> [@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.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [July 4, 2015, 11:22pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/10 "2015-07-04T23:22:38Z")
Correct, updating from the command line will update the docker image, etc.
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [August 22, 2015, 5:51pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/11 "2015-08-22T17:51:18Z")
One of my communities is [189 commits behind at the moment](https://github.com/discourse/discourse/compare/da4c3772...d418c4cfc), 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?
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [August 22, 2015, 6:10pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/12 "2015-08-22T18:10:03Z")
> [@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](https://github.com/discourse/discourse/commit/abd9b26642e477898041be1182e9b33256df1964#diff-e79a60dc6b85309ae70a6ea8261eaf95) (cc @eviltrout) 😉
> [@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](https://meta.discourse.org/t/bundler-always-adds-bundled-with-to-gemfile-lock/29435) 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.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 8, 2024, 12:46pm UTC](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/13 "2024-06-08T12:46:01Z")
This topic was automatically closed after 3276 days. New replies are no longer allowed.