matomo-org / matomo-org/docker

Version 5.0.1 not updated after docker pull

Open
#347 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
1k
Forks
384
PR merge metrics
No merged PRs in 30d

Description

Hi,
I have been using Matomo for a while now.
I pull the latest image from docker hub and the upgrade did not work or was not done?

look at the website message:
![image](https://github.com/matomo-org/docker/assets/44701009/49db589d-5cde-4bf8-9df2-91aa55855459)

In my docker compose file, i specified the version just to be sure:
```yalm
version: '3'

services:
matomo:
image: matomo:5.0.1
container_name: matomo
restart: unless-stopped
volumes:
- matomo_www:/var/www/html
- $PWD/config:/var/www/html/config
# Use MaxMind GeoLite2 databases:
- /var/lib/GeoIP/:/var/www/html/misc/
environment:
- MATOMO_DATABASE_HOST=matomo-mariadb
- MATOMO_DATABASE_ADAPTER=mysql
- MATOMO_DATABASE_TABLES_PREFIX=matomo_
- MATOMO_DATABASE_USERNAME=${MYSQL_USER}
- MATOMO_DATABASE_PASSWORD=${MYSQL_PASSWORD}
- MATOMO_DATABASE_DBNAME=${MYSQL_DATABASE}
- TOKEN_AUTH=${TOKEN_AUTH}
healthcheck:
test: curl http://localhost/index.php?module=API&method=API.getMatomoVersion&token_auth=${TOKEN_AUTH}

```
```shell
docker image ls | grep matomo
matomo 5.0.1 3354df586779 5 days ago 583MB
matomo latest 3354df586779 5 days ago 583MB
``

Am I missing something or is it a bug?

Regards,
Pierre NIKOLOV

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report with the provided docker-compose configuration and the matomo:5.0.1 image, then compare the Docker image tags and digest shown by docker image ls with the version reported by the website. Check whether the upgrade message persists after pulling and recreating the container. Done means the cause is identified and the image or upgrade behavior is corrected or clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.