Version 5.0.1 not updated after docker pull about docker

[alewis001]

I think this might be due to you not running through the upgrade process in the admin pages. The matomo source that's built into the container (in /usr/src/matomo) is copied to the mounted volume (/var/www/html) on startup of the container but only if the matomo source is not already present in that volume. So, even if you're running the 5.0.1 image, if there was already a version of matomo in the volume, let's say v4, then it will be v4 that will actually be served/running until the update process is run.

[bovender]

I ran into the same problem -- pulled a newer image from Docker Hub, but Matomo was stuck in the old version.

The hint with the volume is correct. In my case, I got confused because my docker-compose.yml did not explicitly declare the volume /var/www/html. However, this is done in the upstream Dockerfile:

docker/Dockerfile-debian.template

Line 98 in 8137a71

VOLUME /var/www/html

Thus, upgrading Matomo by pulling an image with a newer tag can never work by itself. The image creates a volume, and Matomo won't upgrade itself because the volume exists.

Steps to remedy this situation:

docker compose stop matomo

# remove the container so the volume is being released
docker compose rm matomo

# remove the volume
# it's hard to find the correct anonymous volume, therefore I use `prune`
# caveat: this may remove other dangling volumes as well!
docker volume prune

# ... do vim-magic or emacs-magic to update the Matomo image tag in your docker-compose.yml ...
# then:
docker compose up -d matomo

IMPORTANT: Think twice before removing the volume! Is all your precious data, e.g. config files, kept safe in separate volumes?

YMMV.