No longer getting notifications for out of date containers

Continuing the discussion from Bundler version warning while updating:

We used to get notified that our container was out of date, and it was time to do the update container dance.

What happened to those warnings?

It still works, what evidence do you have that it does not? There has not been a container update in a while.

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
3eee266…9b102d5 master → origin/master
Updating 3eee266…9b102d5
.gitignore | 1 + | 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

None of those five files are the actual container image, so no rebuild was needed there.

ok… thanks. What fixed the bundler being out of date?

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. 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?

We are pretty good with warnings these days on upgrade. Once every 3-6 month we force people to rebuild from the command line.