# No longer getting notifications for out of date containers
**URL:** https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121
**Category:** Support
**Created:** [8월 14, 2015, 4:40오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121 "2015-08-14T16:40:51Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [8월 14, 2015, 4:40오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/1 "2015-08-14T16:40:51Z")
Continuing the discussion from [Bundler version warning while updating](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238):
> [@Bundler version warning while updating](https://meta.discourse.org/t/bundler-version-warning-while-updating/30238/1):
>
> 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`
We used to get notified that our container was out of date, and it was time to [do the update container dance](https://meta.discourse.org/t/how-do-i-update-my-docker-image-to-latest/23325).
What happened to those warnings?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [8월 14, 2015, 6:07오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/2 "2015-08-14T18:07:04Z")
It still works, what evidence do you have that it does not? There has not been a container update in a while.
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [8월 14, 2015, 6:09오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/3 "2015-08-14T18:09:50Z")
Maybe I’m getting confused between out of date Docker Images (which lead to bundler notices) with the actual container?
The same fix seems to resolve it either way..
> root@share:~# cd /var/discourse/
> root@share:/var/discourse# git pull
> remote: Counting objects: 25, done.
> remote: Compressing objects: 100% (4/4), done.
> remote: Total 25 (delta 11), reused 11 (delta 11), pack-reused 9
> Unpacking objects: 100% (25/25), done.
> From [GitHub - discourse/discourse\_docker: A Docker image for Discourse · GitHub](https://github.com/discourse/discourse_docker)
> 3eee266..9b102d5 master → origin/master
> Updating 3eee266..9b102d5
> Fast-forward
> .gitignore | 1 +
> README.md | 1 -
> image/discourse\_test/Dockerfile | 2 +
> launcher | 30 ++±----
> scripts/docker-gc | 153 ++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 164 insertions(+), 23 deletions(-)
> create mode 100755 scripts/docker-gc
> root@share:/var/discourse# ./launcher rebuild app
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [8월 14, 2015, 9:20오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/4 "2015-08-14T21:20:55Z")
None of those five files are the actual container image, so no rebuild was needed there.
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [8월 14, 2015, 9:38오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/5 "2015-08-14T21:38:29Z")
ok.. thanks. What fixed the bundler being out of date?
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [3월 25, 2017, 4:38오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/6 "2017-03-25T16:38:46Z")
Since I opened this topic, there have been a few times when I received a note that bundler was out of date. I take it to mean that my image is out of date.
Once, an attempt to update then led to the discovery of an [AUFS issue.](https://meta.discourse.org/t/how-to-install-docker-with-aufs-on-linode/39831/4) all because I thought I was going to run a “one-click update.”
Is the assumption about bundler’s version being a part of the container image correct?
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [5월 18, 2019, 10:16오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/7 "2019-05-18T22:16:14Z")
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 18, 2019, 11:36오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/8 "2019-05-18T23:36:43Z")
We are pretty good with warnings these days on upgrade. Once every 3-6 month we force people to rebuild from the command line.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 18, 2019, 11:36오후 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/9 "2019-05-18T23:36:46Z")