Requesting a document that explains how to update Matomo app running on container images

[adelca]

Hi, can you provide a document that describes how to update a Matomo app running on a container image?

My particular case: I am running Matomo fpm-alpine on an EKS cluster + RDS.

I went from matomo:5.1.2-fpm-alpine to matomo:5.2.2-fpm-alpine and the UI still requested me to click on the update button.
There is no documentation about how to update a Matomo container using a new image, the closest I could find is this:
https://matomo.org/faq/on-premise/update-matomo/

Imho, his does not make sense, it says it will download new files which we dont need because I already updated the image.

Also, please consider automation/scripting ways of doing it, having to click on a button after updating Matomo docker image breaks CI/CD concept.

[michalkleiner]

Hi @adelca. Thank you for the suggestion on more documentation.
The container updates the code (the files), but you need to click the update in the UI to also update the version in the database and run any potential upgrade scripts/migrations at the time it most suits you. Just changing the files to newer versions or replacing the container with a newer version of it doesn't constitute a full update. For high traffic instances it is recommended to e.g. stop tracking for a bit or use queued tracking or put Matomo into maintenance mode and run the update from CLI, so it needs to be triggered manually based on how your Matomo instance is used.

[adelca]

Hi @michalkleiner thanks for replying.
Lets ignore high traffic instances for now... Are you saying that the only step needed, is running this command on the command line?
./path/to/matomo/console core:update

Can I do this in an init container (I am running Matomo in a kubernetes pod), before Matomo is running, or I need to exec it while Matomo app is running?

I still think a specific doc for docker containers (and Kubernetes maybe) would be of great help to many other people.

[michalkleiner]

When you say "Matomo is running", what exactly do you mean? It's a stateless web application, so it's not running per se. It's responding to requests and returns markup or API responses. As long as you can access the CLI and Matomo can access the database and respond to requests, you can run the console command.

[Prinzhorn]

Currently in the same boat and also found #354, which this issue is kind of a duplicate of.

@michalkleiner can you confirm that these are the steps that need to be taken to upgrade Matomo when run via Docker:

1. Update the image version to get the new code and launch the the image
2. Click the update button to run migrations

Looking at https://matomo.org/faq/on-premise/update-matomo/ and specifically the "The Manual Three-Step Update" I would assume updating the image is the same as "Replace the Matomo files with the latest version". I updated the version in docker-compose.yml. docker ps says the running image is "matomo:5.4.0-apache" (I was on 5.1.0 before). But still I'm seeing:

and NOT

What the docs say. So why does it think I'm still on 5.1.0 when the code is now 5.4.0?

Edit: alright, clicking the upgrade button seemed to have worked. I assume upgrading the image is not enough because the volume still has outdated stuff. IDK, that's why we're asking for docs.

[rspu]

In the same boat here. Update procedure doesn't make any sense to me. I would have expected that updating the docker image (maybe followed by a console core:update) should be enough to update Matomo to an new version (I have disabled automatic updates in the config.ini.php because I wan't do it programmatically).

Instead after deploying the new docker image the UI still show the old version and if you then do the update from the UI (which means I have to first enable automatic update in config.ini.php again) it will download some ZIP File before doing any DB updates. I guess the ZIP File is the application source code which should already be included in the docker image? Very confusing and inconvenient.

[Profecy]

This is bad. I just had to recover my Matomo instance from backup because the latest docker image is version 5.6.1, but hitting the upgrade button inside Matomo updated my database and the application to 5.6.2. After I restarted the container, Matomo was broken because now it was running version 5.6.1 again but the database had already been upgraded to 5.6.2... How come the docker images are one version behind the actual software? I am using the "latest" tag, so I would expect it to have the latest version of Matomo.