docker pull mediawiki 

# Quick reference

• Maintained by:
  Wikimedia Foundation & Docker Community

• Where to get help:
  the Docker Community Forums, the Docker Community Slack, or Stack Overflow

Supported tags and respective Dockerfile links

• 1.35.0, 1.35, lts, stable, latest
• 1.35.0-fpm, 1.35-fpm, lts-fpm, stable-fpm
• 1.35.0-fpm-alpine, 1.35-fpm-alpine, lts-fpm-alpine, stable-fpm-alpine
• 1.34.4, 1.34, legacy
• 1.34.4-fpm, 1.34-fpm, legacy-fpm
• 1.34.4-fpm-alpine, 1.34-fpm-alpine, legacy-fpm-alpline
• 1.31.10, 1.31, legacylts
• 1.31.10-fpm, 1.31-fpm, legacylts-fpm
• 1.31.10-fpm-alpine, 1.31-fpm-alpine, legacylts-fpm-alpine

Quick reference (cont.)

• Where to file issues:
  https://phabricator.wikimedia.org/project/view/3094/

• Supported architectures: (more info)
  amd64, arm32v5, arm32v6, arm32v7, arm64v8, i386, ppc64le

• Published image artifact details:
  repo-info repo's repos/mediawiki/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/mediawiki
  official-images repo's library/mediawiki file (history)

• Source of this description:
  docs repo's mediawiki/ directory (history)

What is MediaWiki?

MediaWiki is free and open-source wiki software. Originally developed by Magnus Manske and improved by Lee Daniel Crocker, it runs on many websites, including Wikipedia, Wiktionary and Wikimedia Commons. It is written in the PHP programming language and stores the contents into a database. Like WordPress, which is based on a similar licensing and architecture, it has become the dominant software in its category.

wikipedia.org/wiki/MediaWiki

How to use this image

The basic pattern for starting a mediawiki instance is:

$ docker run --name some-mediawiki -d mediawiki

If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:

$ docker run --name some-mediawiki -p 8080:80 -d mediawiki

Then, access it via http://localhost:8080 or http://host-ip:8080 in a browser.

There are multiple database types supported by this image, most easily used via standard container linking. In the default configuration, SQLite can be used to avoid a second container and write to flat-files. More detailed instructions for different (more production-ready) database types follow.

When first accessing the webserver provided by this image, it will go through a brief setup process. The details provided below are specifically for the "Set up database" step of that configuration process.

MySQL

$ docker run --name some-mediawiki --link some-mysql:mysql -d mediawiki

• Database type: MySQL, MariaDB, or equivalent
• Database name/username/password: <details for accessing your MySQL instance> (MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE; see environment variables in the description for mariadb)
• ADVANCED OPTIONS; Database host: some-mysql (for using the /etc/hosts entry added by --link to access the linked container's MySQL instance)

Volumes

By default, this image does not include any volumes.

The paths /var/www/html/images and /var/www/html/LocalSettings.php are things that generally ought to be volumes, but do not explicitly have a VOLUME declaration in this image because volumes cannot be removed.

$ docker run --rm mediawiki tar -cC /var/www/html/sites . | tar -xC /path/on/host/sites

... via docker stack deploy or docker-compose

Example stack.yml for mediawiki:

# MediaWiki with MariaDB
#
# Access via "http://localhost:8080"
#   (or "http://$(docker-machine ip):8080" if using docker-machine)
version: '3'
services:
  mediawiki:
    image: mediawiki
    restart: always
    ports:
      - 8080:80
    links:
      - database
    volumes:
      - /var/www/html/images
      # After initial setup, download LocalSettings.php to the same directory as
      # this yaml and uncomment the following line and use compose to restart
      # the mediawiki service
      # - ./LocalSettings.php:/var/www/html/LocalSettings.php
  database:
    image: mariadb
    restart: always
    environment:
      # @see https://phabricator.wikimedia.org/source/mediawiki/browse/master/includes/DefaultSettings.php
      MYSQL_DATABASE: my_wiki
      MYSQL_USER: wikiuser
      MYSQL_PASSWORD: example
      MYSQL_RANDOM_ROOT_PASSWORD: 'yes'

Run docker stack deploy -c stack.yml mediawiki (or docker-compose -f stack.yml up), wait for it to initialize completely, and visit http://swarm-ip:8080, http://localhost:8080, or http://host-ip:8080 (as appropriate).

Adding additional libraries / extensions

This image does not provide any additional PHP extensions or other libraries, even if they are required by popular plugins. There are an infinite number of possible plugins, and they potentially require any extension PHP supports. Including every PHP extension that exists would dramatically increase the image size.

If you need additional PHP extensions, you'll need to create your own image FROM this one. The documentation of the php image explains how to compile additional extensions.

The following Docker Hub features can help with the task of keeping your dependent images up-to-date:

• Automated Builds let Docker Hub automatically build your Dockerfile each time you push changes to it.

Image Variants

The mediawiki images come in many flavors, each designed for a specific use case.

mediawiki:<version>

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.

mediawiki:<version>-alpine

This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.

This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.

To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's mediawiki/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.