Docker update workflow when Matomo UI reports newer version

Support & Bugs
1

Hi,

I am running Matomo on an ARM64 VPS using the official Docker image, managed through Portainer.

Setup:

  • Image: matomo:latest

  • Host architecture: ARM64

  • Database: MariaDB 10.11 in Docker

  • Reverse proxy: Apache

  • Matomo files/config/plugins persisted via mounted volume

When Portainer shows an available image update, I recreate the Matomo container with “pull latest image” enabled. The container updates and Matomo keeps working.

However, after doing this, the Matomo web UI may still report that a newer Matomo version is available, for example 5.11.2. Updating through the Matomo web UI works, but then the Matomo application files seem to be ahead of the Docker image version/metadata.

I found a few older forum threads about Docker image updates and version mismatches, but I am still unsure about the recommended current workflow.

For Docker-based Matomo installs, should we:

  1. Only update by pulling/recreating the Docker image and wait until matomo:latest contains the newest Matomo release, or

  2. Use the Matomo web updater when the UI reports a newer version, even if the Docker image appears to lag behind?

Is there any special consideration for ARM64 images or multi-architecture tags?

Thanks.