# 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:** [2015年八月14日 16: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:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**Post date:** [2015年八月14日 16:40 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/1 "2015-08-14T16:40:51Z")

</div>

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?

---

_[View the full topic](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121)._