diff --git a/bitnami/matomo/5/debian-12/Dockerfile b/bitnami/matomo/5/debian-12/Dockerfile index 9ff54bad328f..627b3073a094 100644 --- a/bitnami/matomo/5/debian-12/Dockerfile +++ b/bitnami/matomo/5/debian-12/Dockerfile @@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith" ARG TARGETARCH LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2026-02-24T12:40:34Z" \ + org.opencontainers.image.created="2026-03-03T08:51:49Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/matomo/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/matomo" \ @@ -23,19 +23,19 @@ ENV HOME="/" \ COPY prebuildfs / SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"] # Install required system packages and dependencies -RUN install_packages acl ca-certificates cron curl libaudit1 libbrotli1 libbsd0 libbz2-1.0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libexpat1 libffi8 libfftw3-double3 libfontconfig1 libfreetype6 libgcc-s1 libgcrypt20 libglib2.0-0 libgmp10 libgnutls30 libgomp1 libgpg-error0 libgssapi-krb5-2 libhashkit2 libhogweed6 libicu72 libidn2-0 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.5-0 libldap-common liblqr-1-0 libltdl7 liblzma5 libmagickcore-6.q16-6 libmagickwand-6.q16-6 libmd0 libmemcached11 libncurses6 libnettle8 libnghttp2-14 libonig5 libp11-kit0 libpam0g libpcre2-8-0 libpcre3 libpng16-16 libpq5 libpsl5 libreadline8 librtmp1 libsasl2-2 libsodium23 libsqlite3-0 libssh2-1 libssl3 libstdc++6 libsybdb5 libtasn1-6 libtidy5deb1 libtinfo6 libunistring2 libuuid1 libwebp7 libx11-6 libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxslt1.1 libzip4 libzstd1 openssl procps rsync zlib1g +RUN install_packages acl ca-certificates cron curl libaudit1 libbrotli1 libbsd0 libbz2-1.0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libexpat1 libffi8 libfftw3-double3 libfontconfig1 libfreetype6 libgcc-s1 libgcrypt20 libglib2.0-0 libgmp10 libgnutls30 libgomp1 libgpg-error0 libgssapi-krb5-2 libhashkit2 libhogweed6 libicu72 libidn2-0 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.5-0 libldap-common liblqr-1-0 libltdl7 liblzma5 libmagickcore-6.q16-6 libmagickwand-6.q16-6 libmd0 libmemcached11 libncurses6 libnettle8 libnghttp2-14 libonig5 libp11-kit0 libpam0g libpcre2-8-0 libpcre3 libpng16-16 libpsl5 libreadline8 librtmp1 libsasl2-2 libsodium23 libsqlite3-0 libssh2-1 libssl3 libstdc++6 libsybdb5 libtasn1-6 libtidy5deb1 libtinfo6 libunistring2 libuuid1 libwebp7 libx11-6 libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxslt1.1 libzip4 libzstd1 openssl procps rsync zlib1g RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \ DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \ mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \ COMPONENTS=( \ "render-template-1.0.9-162-linux-${OS_ARCH}-debian-12" \ - "php-8.4.18-1-linux-${OS_ARCH}-debian-12" \ - "apache-2.4.66-0-linux-${OS_ARCH}-debian-12" \ + "php-8.4.18-7-linux-${OS_ARCH}-debian-12" \ + "apache-2.4.66-1-linux-${OS_ARCH}-debian-12" \ "mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \ - "postgresql-lib-18.2.0-0-linux-${OS_ARCH}-debian-12" \ - "libphp-8.4.18-2-linux-${OS_ARCH}-debian-12" \ + "postgresql-lib-18.3.0-0-linux-${OS_ARCH}-debian-12" \ + "libphp-8.4.18-5-linux-${OS_ARCH}-debian-12" \ "ini-file-1.4.9-7-linux-${OS_ARCH}-debian-12" \ - "matomo-5.7.1-0-linux-${OS_ARCH}-debian-12" \ + "matomo-5.7.1-1-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -62,7 +62,7 @@ ENV APACHE_HTTPS_PORT_NUMBER="" \ APACHE_HTTP_PORT_NUMBER="" \ APP_VERSION="5.7.1" \ BITNAMI_APP_NAME="matomo" \ - IMAGE_REVISION="5" \ + IMAGE_REVISION="6" \ LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \ PATH="/opt/bitnami/common/bin:/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/apache/bin:/opt/bitnami/mysql/bin:/opt/bitnami/postgresql-lib/bin:$PATH" diff --git a/bitnami/matomo/README.md b/bitnami/matomo/README.md index ee33001ef807..826f666c8a2c 100644 --- a/bitnami/matomo/README.md +++ b/bitnami/matomo/README.md @@ -1,13 +1,11 @@ # Bitnami Secure Image for Matomo -## What is Matomo? - > Matomo, formerly known as Piwik, is a real time web analytics program. It provides detailed reports on website visitors. [Overview of Matomo](https://matomo.org/) Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement. -## TL;DR +## TL;DR ```console docker run --name matomo bitnami/matomo:latest @@ -16,7 +14,7 @@ docker run --name matomo bitnami/matomo:latest **Warning**: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the [Environment Variables](#environment-variables) section for a more secure d eployment. -## Why use Bitnami Secure Images? +## Why use Bitnami Secure Images? Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images? @@ -33,15 +31,15 @@ Each image comes with valuable security metadata. You can view the metadata in [ If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy). -## Why use a non-root container? +## Why use a non-root container? Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html). -## Supported tags and respective `Dockerfile` links +## Supported tags and respective `Dockerfile` links Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html). -## How to get this image +## How to get this image The recommended way to get the Bitnami Matomo Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/matomo/). To use a specific version, you can pull a versioned tag. Find the [list of available versions] () in the Docker Hub Registry. @@ -58,15 +56,15 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM docker build -t bitnami/APP:latest . ``` -## How to use this image +## How to use this image Matomo requires access to a MySQL database or MariaDB database to store information. It uses our [MariaDB image] () for the database requirements. -### Run the application using Docker Compose +### Run the application using Docker Compose Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/matomo). -### Persisting your application +### Persisting your application If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed. @@ -76,11 +74,15 @@ The above examples define docker volumes namely `mariadb_data` and `matomo_data` To avoid inadvertent removal of these volumes you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data. -> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`. +> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`. -## Configuration +## Configuration -### Environment variables +The following section describes the supported environment variables + +### Environment variables + +The following tables list the main variables you can set. #### Customizable environment variables @@ -170,7 +172,7 @@ This would be an example of reverse proxy configuration: The `MATOMO_SMTP_*` environment variables allows you configure the SMTP settings in the application. Please take a look at the environment variables information above for more information. -### Backing up your container +### Backing up your container To backup your data, configuration and logs, follow these simple steps: @@ -195,7 +197,7 @@ docker run --rm -v /path/to/matomo-backups:/backups --volumes-from matomo busybo cp -a /bitnami/matomo /backups/latest ``` -### Restoring a backup +### Restoring a backup Restoring a backup is as simple as mounting the backup as volumes in the containers. @@ -219,7 +221,7 @@ For the Matomo container: bitnami/matomo:latest ``` -## Upgrading Matomo +## Upgrading Matomo Bitnami provides up-to-date versions of MariaDB and Matomo, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the Matomo container. For the MariaDB upgrade you can take a look at @@ -254,17 +256,17 @@ Bitnami provides up-to-date versions of MariaDB and Matomo, including security p - For docker-compose: `$ docker-compose up matomo` - For manual execution (mount the directories if needed): `docker run --name matomo bitnami/matomo:latest` -### FIPS configuration in Bitnami Secure Images +### FIPS configuration in Bitnami Secure Images The Bitnami Matomo Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables: - `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`. -## Customize this image +## Customize this image The Bitnami Matomo Docker image is designed to be extended so it can be used as the base image for your custom web applications. -### Extend this image +### Extend this image Before extending this image, please note there are certain configuration settings you can modify using the original image: @@ -277,11 +279,11 @@ If your desired customizations cannot be covered using the methods mentioned abo ```Dockerfile FROM bitnami/matomo -### Put your customizations below +### Put your customizations below ... ``` -## Notable Changes +## Notable Changes ## 4.15.0-debian-11-r20 @@ -315,7 +317,7 @@ To upgrade a previous Bitnami Matomo container image, which did not support non- - The PHP configuration volume (`/bitnami/php`) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the PHP configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom PHP configuration files are advised to mount a volume for the configuration at `/opt/bitnami/php/conf`, or mount specific configuration files individually. - Enabling custom Apache certificates by placing them at `/opt/bitnami/apache/certs` has been deprecated, and support for this functionality will be dropped in the near future. Users wanting to enable custom certificates are advised to mount their certificate files on top of the preconfigured ones at `/certs`. -## License +## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.