Matomo 5.0.0 is not available on Dockerhub

[law]

Matomo 5.0.0 is not available on Dockerhub

[michalkleiner]

Hi @law, yes, there's usually 1-2 days delay after a Matomo release is published as the release processes are not connected and are run by different maintainers. Please check back again in a day or two.

/ping @J0WI

[Nitwel]

Oh, I'm using docker and I've pressed the update to 5.0 button but now I get a Error 500 though the server isn't logging any errors. Does someone maybe know how to roll back to 4.16 as now matomo is broken for me.

[michalkleiner]

@Nitwel I don't think it'd be related, updating to 5.0.0 via the UI and using a new docker image including Matomo 5.0.0 (that is not released yet) are two separate issues.

Do you see any errors/any extra information when you enable development mode temporarily?

[Nitwel]

Maybe, what I was thinking is that this issue might solve itself when the v5.0 docker image releases and updating to that makes matomo work again. I've added logging and enabled the developer mode but I'm not getting any error messages to show up either in the terminal nor in the logs file that doesn't get created.

[Nitwel]

Okay, I was able to make matomo run again by completely resetting the mounted files and installing it onto the existing database again. In case someone else tried to update to version 5.0.0 using docker at the moment, that's what you can do, but make sure to back up your old files!

[johnthomas00]

5.0.0 was apparently built successfully a couple of days ago, but is still not in dockerhub.
https://github.com/matomo-org/docker/actions/runs/7260092597/job/19778561735
https://hub.docker.com/_/matomo/tags

[J0WI]

https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what

[law]

Thanks all, I see that Docker Hub has been updated with the Matomo 5 images. However - and I freely admit this might be a PEBKAC problem - I can't see to get my local docker-compose to update and grab the new images.

A quick 'docker compose pull' in the same directory as my docker-compose.yml file claims I've pulled the latest, but a check with container inspect shows the Matomo 4.16 image:

docker container inspect matomo-app-1 | jq -r '.[].Image'
sha256:e3436d993b559d08937cce5092d26411a9942643d8cd4fa6c7ca53ff2cb7838c

Per Dockerhub, I would expect a matomo:fpm-alpine hash of cd1c43eb4bd for the one built with Matomo 5.

I've tried various methods of clearing this, including stopping Matomo (docker compose down), clearing the images but saving the volumes (docker system prune -f -a), and re-pulling with docker compose pull, but I can't get a newer image hash than e3436d993b55. Full command list and output here

This is on a fairly standard/straightforward Ubuntu 22.04.3 host, x86_64 kernel, 5:24.0.7-1~ubuntu.22.04~jammy docker-ce package from the official download.docker.com repo, etc.

I am surely missing something very simple here, but I'll be darned if I can figure out what.

[J0WI]

Closing due docker-library/official-images@5553b14