Dockerized MediaWiki build on top of docker-mediawiki-base images in the style of the official MediaWiki Docker images with preinstalled Composer, MediaWiki and Xdebug (switched off by default, see below). Released on dockerhub. This image is intended to be used during development, testing and CI workflows.
$wgServer = http://localhost:8080- Wiki Admin: WikiSysop
- Password: wiki4everyone
| MediaWiki | PHP | Composer | Node.js | npm | MariaDB client | Xdebug | docker-mediawiki-tools |
|---|---|---|---|---|---|---|---|
| 1.47-dev-08aa667 (pre-release) | 8.5.12 (default) | 2.11.1 | 24.22.3 | 11.19.1 | 1:11.8.6-0+deb13u1 | 3.5.3 | 5.3.1 |
| 1.46.2 | 8.5.12 | 2.11.1 | 24.22.3 | 11.19.1 | 1:11.8.6-0+deb13u1 | 3.5.3 | 5.3.1 |
| 1.46.2 | 8.4.27 (default) | 2.11.1 | 24.22.3 | 11.19.1 | 1:11.8.6-0+deb13u1 | 3.5.3 | 5.3.1 |
| 1.43.11 | 8.3.36 (default) | 2.11.1 | 24.22.3 | 11.19.1 | 1:11.8.6-0+deb13u1 | 3.5.3 | 5.3.1 |
The table is generated by update_readme_table.sh from the labels of the published gesinn/mediawiki-ci images; do not edit it by hand. (default) marks the PHP version used for tags without a PHP part (e.g. 1.43). gesinn/mediawiki carries the same versions, but neither Xdebug, nor the tools, nor Node.js and npm: only gesinn/mediawiki-ci has Node.js and npm, taken from the official node image. The MariaDB client is the Debian package version (including the security patch level). n/a means that the published image does not carry the label yet. The combinations are the entries of matrix.json. The versions of Composer, Xdebug and docker-mediawiki-tools are pinned in the Dockerfile and kept up to date by Renovate. Xdebug has one version for all PHP versions (Xdebug 3.5 supports PHP 8.2 to 8.5).
In gesinn/mediawiki-ci, Xdebug is loaded but switched off (XDEBUG_MODE=off), so PHPUnit runs at full speed. Enable it per run with the environment variable, which takes precedence over the ini file:
# docker compose override
services:
wiki:
environment:
XDEBUG_MODE: coverage # or debug, develop, ...PCOV is installed in the image as well, but not enabled. It collects line coverage several times faster than Xdebug. To use it:
docker-php-ext-enable pcov # as root
echo 'pcov.directory=/var/www/html/extensions/MyExtension' >> /usr/local/etc/php/conf.d/docker-php-ext-pcov.iniWithout pcov.directory, PCOV looks for src, lib or app below the working directory and finds nothing when PHPUnit runs from the MediaWiki root.
The versions are also available as image labels and as annotations on the multi-arch index, so they can be read without pulling the image:
docker buildx imagetools inspect gesinn/mediawiki-ci:1.43-php8.2 --format '{{json .Manifest.Annotations}}'
| Label | Content |
|---|---|
org.opencontainers.image.base.name, org.opencontainers.image.base.digest |
gesinn/mediawiki-base image the build used, and its digest |
org.opencontainers.image.version, it.gesinn.mediawiki.version |
MediaWiki version |
it.gesinn.php.version |
effective PHP version, e.g. 8.2.34 |
it.gesinn.composer.version |
Composer version |
it.gesinn.xdebug.version |
Xdebug version (mediawiki-ci only) |
it.gesinn.<package>.version |
installed Debian package version of every package the Dockerfile adds (sudo, unzip, less, nano, wget, mariadb-client, plus libpq-dev in mediawiki-ci); the list is INSTALLED_PACKAGES in helpers.sh |
it.gesinn.nodejs.version, it.gesinn.npm.version |
version of the node and npm binaries (mediawiki-ci only, from the official node image) |
it.gesinn.tools.version |
version of docker-mediawiki-tools (mediawiki-ci only) |
matrix.json is the list of the combinations that are built, one entry per MediaWiki and PHP version, with the PHP version that the tags without a PHP part (e.g. 1.43) point to:
{"mediawiki_version": "1.43", "php_version": "8.3", "php_default": "8.3"}Every entry is built for both image types, mediawiki and mediawiki-ci. A push to main builds all entries. A manual run (workflow_dispatch) can be restricted to one MediaWiki and / or PHP version; the combination has to be in matrix.json, otherwise the run stops in the plan job. docker-mediawiki-base triggers this workflow for the combinations of its own matrix.json that have "downstream": true: an entry that is added or removed there has to be added or removed here as well.
Composer does not block the image build on security advisories (policy.advisories.block is false): a finding in a dev dependency, which the mediawiki image does not even install, must not stop a build. Instead the build runs an audit gate (audit-gate.php) after composer update:
| Image | Gate | Effect |
|---|---|---|
mediawiki |
strict, installed (non-dev) packages |
high or critical advisories fail the build, everything else is reported as a warning |
mediawiki-ci |
warn, including the dev tools |
all advisories are reported, none fails the build |
Advisories without a severity are treated as warnings. The warnings are part of the build log.
A high or critical advisory that cannot be fixed (e.g. because MediaWiki pins the vulnerable version) is accepted in audit-triage.json, with a reason and a date to review it again:
{
"PKSA-xxxx-xxxx-xxxx": { "reason": "why this is acceptable for now", "review": "2026-12-01" }
}Accepted advisories are still printed. An expired review date is printed as a warning, it never fails a build.
/etc/apache/usr/local/etc/php/