Icewhale's ZimaBoard/ZimaBoard2 docker/app isn't "current" or "updating"

Help
, ,
1

Was referred here by Support folks @ NetData

Problem/Question - Problem I am having is the client/docker app that is installed via the “store” via interface isn’t upgrading or pulling to the current/latest client for NetData.

Relevant docs you followed/actions you took to solve the issue: Per support I stopped the App/Container through the web interface and change it from “Latest” to “Stable” build and restarted. It still is running the same version (v2.8.1) and will not update, nowhere near 2.9 or 2.10.

Environment/Browser/Agent’s version etc: Doesn’t matter which browser - problem seems to be on the container settings or something - it just never updates.

What I expected to happen: I would expect the update to be coming down through the system just like all of the other “apps” do (they are basically docker based and should just pull the current build).

2

The issue here is standard Docker behaviour rather than a Netdata problem. When you stop and restart a container, Docker doesn’t check for a newer image, it just restarts using the same locally cached image. Switching the tag in the UI also won’t trigger a new pull.

To update, you need to explicitly pull the new image first:

docker pull netdata/netdata:stable

Then stop and recreate the container. Your configuration and historical data will be preserved through the volume mounts.

If you’re looking for something more automatic, you can use Watchtower, which monitors your containers and pulls new images automatically when they’re available:

docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  containrrr/watchtower \
  netdata
3

Thanks for the detailed explanation and suggestions. I’m not sure if I’ll be able to run those commands from Icewhale’s terminal, as it’s a bit limited, but I’ll give it a try when I get home and will let you know how it goes. Appreciate your help!