# 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:** 6

<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:** [2017年三月25日 16:38 UTC](https://meta.discourse.org/t/no-longer-getting-notifications-for-out-of-date-containers/32121/6 "2017-03-25T16:38:46Z")

</div>

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?

---

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