Rebuild needed on Docker Hub
Saboteur777 opened this issue · 13 comments
The latest available tag for official Matomo Docker Hub image is 3.7: https://hub.docker.com/_/matomo?tab=tags
Please tag a new Docker image to include version 3.8.
Yes, please – sounds like there are some pretty critical security fixes in 3.8!
They were busy this week with rebuilding all images for CVE-2019-3462. I've now opened docker-library/official-images#5345 to call their attention.
Please be aware that 3.8.0 has a bug in the upgrade process: matomo-org/matomo#13836. This will be fixed in 3.8.1.
Shall we ask to go to 3.8.1 directly or is there a PR for it aswell ?
3.8.1 will be released very soon (probably today), so I'd say building 3.8.1 directly should be possible
Actually the update reminder on my homepage tell me it is available, but since I'm using Docker images, I can't update tho ;)
Actually the update reminder on my homepage tell me it is available, but since I'm using Docker images, I can't update tho ;)
You actually can update Matomo even inside Docker.
What about static files in the image if my container get rescheduled ?
You need to use a persistent volume to keep the files.
I agree to keep the config in a volume, but what about website static files, possibly new needed packages in the image.
Update a container app through an UI when using Docker is not a best practice.
Update a container app through an UI when using Docker is not a best practice.
@zaggash Totally agree, that's why I've created an other image for Matomo because of this (see also #97).
See also this issue on the main repo (matomo-org/matomo#12988) to try to solve this but @tsteur and @mattab do not agree with my statement unfortunately.
That is unfortunate.
At this point the image is not designed to run on a cluster as is.
@crazy-max Did you try to persist the plugin folder ? what is the drawback ?
@zaggash Everything is persisted as intended (configuration, installed plugins (not core ones), tmp, sessions and user folders to store your custom logo). Ready to go on a cluster, see swarm and k8s examples.
For plugins I have to use inotify to watch and move plugins in data folder...
Closed by docker-library/official-images#5345