J0WI

You don't need cron in Docker containers. Just use cron or systemd timers on your host system that executes something like `docker exec -u www-data some-piwik php console`.

> To me, I would find helpful if this image came with cron installed [Busybox](https://hub.docker.com/_/busybox), which is already included in the Alpine variant, ships with a cron daemon.

The Alpine variant contains BusyBox with the [crond applet](https://www.busybox.net/downloads/BusyBox.html#crond). You can mount a cron file into `/var/spool/cron/crontabs` and start a container with `busybox crond -f`.

You can easily mount you own config into `/usr/local/etc/php-fpm.d/`, but UNIX socket are not really made for containers. You can scale the application by spawning additional containers and balance the...

I'd prefer using the package from distros. Is this possible with Matomo?

For the reference: https://packages.debian.org/stretch/all/ttf-unifont/filelist https://pkgs.alpinelinux.org/contents?branch=v3.9&name=unifont&arch=s390x&repo=main

Bruce cron runs as deamon while [BusyBox](https://www.busybox.net/) cron can also run in a foreground process e.g. as sidecar container.

> try to apply for all Perl versions (maybe via Dockerfile.template) Replacing `generate.pl` with an `update.sh` to integrate @docker-library-bot would be an other improvement.

The @docker-library-bot can trigger an `update.sh` to update Perl and generate Dockerfiles. Just add it to https://github.com/docker-library/oi-janky-groovy/blob/master/update.sh/vars.groovy and give @docker-library-bot commit access.

This does only partially fix the problem. It's hard to customize the `CMD` if it's a whole script. Normally you can pass your own command or flags to a Docker...