Introducing our new CEO Don Johnson - Read More

bitnami/mediawiki

Verified Publisher

By VMware

Updated 7 months ago

🛑 DEPRECATED Bitnami Docker Image for MediaWiki

Image
Content Management System
Integration & Delivery
Security
28

5M+

Bitnami package for MediaWiki

🛑 Deprecation Notice

The Mediawiki container is now deprecated. This image will no longer be released in our catalog, but already-released container images will persist in the registries.

After some months, this repository will be removed in favor of bitnami/mediawiki-archived where all existing images can be found.

What is MediaWiki?

MediaWiki is the free and open source wiki software that powers Wikipedia. Used by thousands of organizations, it is extremely powerful, scalable software and a feature-rich wiki implementation.

Overview of MediaWiki 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

docker run --name mediawiki bitnami/mediawiki: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 section for a more secure d eployment.

Why use Bitnami Images?

  • Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
  • With Bitnami images the latest bug fixes and features are available as soon as possible.
  • Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
  • All our images are based on minideb -a minimalist Debian based container image that gives you a small base container image and the familiarity of a leading Linux distribution- or scratch -an explicitly empty image-.
  • All Bitnami images available in Docker Hub are signed with Notation. Check this post to know how to verify the integrity of the images.
  • Bitnami container images are released on a regular basis with the latest distribution packages available.

Looking to use MediaWiki in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.

How to deploy MediaWiki in Kubernetes?

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami MediaWiki Chart GitHub repository.

Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.

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.

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.

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

Subscribe to project updates by watching the bitnami/containers GitHub repo.

Get this image

The recommended way to get the Bitnami MediaWiki Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/mediawiki:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/mediawiki:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .

How to use this image

MediaWiki requires access to a MySQL or MariaDB database to store information. We'll use the Bitnami Docker Image for MariaDB for the database requirements.

Using the Docker Command Line

Step 1: Create a network

docker network create mediawiki-network

Step 2: Create a volume for MariaDB persistence and create a MariaDB container

$ docker volume create --name mariadb_data
docker run -d --name mariadb \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env MARIADB_USER=bn_mediawiki \
  --env MARIADB_PASSWORD=bitnami \
  --env MARIADB_DATABASE=bitnami_mediawiki \
  --network mediawiki-network \
  --volume mariadb_data:/bitnami/mariadb \
  bitnami/mariadb:latest

Step 3: Create volumes for MediaWiki persistence and launch the container

$ docker volume create --name mediawiki_data
docker run -d --name mediawiki \
  -p 8080:8080 -p 8443:8443 \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env MEDIAWIKI_DATABASE_USER=bn_mediawiki \
  --env MEDIAWIKI_DATABASE_PASSWORD=bitnami \
  --env MEDIAWIKI_DATABASE_NAME=bitnami_mediawiki \
  --network mediawiki-network \
  --volume mediawiki_data:/bitnami/mediawiki \
  bitnami/mediawiki:latest

Access your application at http://your-ip/

Run the application using Docker Compose
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/mediawiki/docker-compose.yml > docker-compose.yml
docker-compose up -d

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.

If you detect any issue in the docker-compose.yaml file, feel free to report it or contribute with a fix by following our Contributing Guidelines.

Persisting your application

If you remove the container all your data 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.

For persistence you should mount a directory at the /bitnami/mediawiki path. If the mounted directory is empty, it will be initialized on the first run. Additionally you should mount a volume for persistence of the MariaDB data.

The above examples define the Docker volumes named mariadb_data and mediawiki_data. The MediaWiki application state will persist as long as volumes are not removed.

To avoid inadvertent removal of volumes, you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

Mount host directories as data volumes with Docker Compose

This requires a minor change to the docker-compose.yml file present in this repository:

   mariadb:
     ...
     volumes:
-      - 'mariadb_data:/bitnami/mariadb'
+      - /path/to/mariadb-persistence:/bitnami/mariadb
   ...
   mediawiki:
     ...
     volumes:
-      - 'mediawiki_data:/bitnami/mediawiki'
+      - /path/to/mediawiki-persistence:/bitnami/mediawiki
   ...
-volumes:
-  mariadb_data:
-    driver: local
-  mediawiki_data:
-    driver: local

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Mount host directories as data volumes using the Docker command line

Step 1: Create a network (if it does not exist)

docker network create mediawiki-network

Step 2. Create a MariaDB container with host volume

docker run -d --name mariadb \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env MARIADB_USER=bn_mediawiki \
  --env MARIADB_PASSWORD=bitnami \
  --env MARIADB_DATABASE=bitnami_mediawiki \
  --network mediawiki-network \
  --volume /path/to/mariadb-persistence:/bitnami/mariadb \
  bitnami/mariadb:latest

Step 3. Create the MediaWiki container with host volumes

docker run -d --name mediawiki \
  -p 8080:8080 -p 8443:8443 \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env MEDIAWIKI_DATABASE_USER=bn_mediawiki \
  --env MEDIAWIKI_DATABASE_PASSWORD=bitnami \
  --env MEDIAWIKI_DATABASE_NAME=bitnami_mediawiki \
  --network mediawiki-network \
  --volume /path/to/mediawiki-persistence:/bitnami/mediawiki \
  bitnami/mediawiki:latest

Configuration

Environment variables

Customizable environment variables

NameDescriptionDefault Value
MEDIAWIKI_DATA_TO_PERSISTFiles to persist relative to the MediaWiki installation directory. To provide multiple values, separate them with a whitespace.images extensions skins LocalSettings.php
MEDIAWIKI_SKIP_BOOTSTRAPWhether to perform initial bootstrapping for the application.nil
MEDIAWIKI_WIKI_NAMEMediaWiki wiki name.Bitnami MediaWiki
MEDIAWIKI_WIKI_PREFIXBase path to use for MediaWiki wiki URLs./wiki
MEDIAWIKI_SCRIPT_PATHBase path to use for MediaWiki script URLs.nil
MEDIAWIKI_HOSTMediaWiki application host.localhost
MEDIAWIKI_ENABLE_HTTPSWhether to use HTTPS by default.no
MEDIAWIKI_EXTERNAL_HTTP_PORT_NUMBERPort to used by MediaWiki to generate URLs and links when accessing using HTTP.80
MEDIAWIKI_EXTERNAL_HTTPS_PORT_NUMBERPort to used by MediaWiki to generate URLs and links when accessing using HTTPS.443
MEDIAWIKI_USERNAMEMediaWiki user name.user
MEDIAWIKI_PASSWORDMediaWiki user password.bitnami123
MEDIAWIKI_EMAILMediaWiki user e-mail address.user@example.com
MEDIAWIKI_SMTP_HOSTMediaWiki SMTP server host.nil
MEDIAWIKI_SMTP_HOST_IDMediaWiki SMTP server host ID. It is a MediaWiki-specific setting used to build the Message-ID email header. If not provided, it will default to the value of MEDIAWIKI_SMTP_HOST.$MEDIAWIKI_SMTP_HOST
MEDIAWIKI_SMTP_PORT_NUMBERMediaWiki SMTP server port number.nil
MEDIAWIKI_SMTP_USERMediaWiki SMTP server user (if being used).nil
MEDIAWIKI_SMTP_PASSWORDMediaWiki SMTP server user password (if being used).nil
MEDIAWIKI_ENABLE_SMTP_AUTHWhether to use authentication for SMTP server. Valid values: yes, no.yes
MEDIAWIKI_DATABASE_HOSTDatabase server host.mariadb
MEDIAWIKI_DATABASE_PORT_NUMBERDatabase server port.3306
MEDIAWIKI_DATABASE_NAMEDatabase name.bitnami_mediawiki
MEDIAWIKI_DATABASE_USERDatabase user name.bn_mediawiki
MEDIAWIKI_DATABASE_PASSWORDDatabase user password.nil
MEDIAWIKI_SKIP_CONFIG_VALIDATIONSkip config validation during startup. Allows the use of deprecated values in MediaWiki configuration file.no

Read-only environment variables

NameDescriptionValue
MEDIAWIKI_BASE_DIRMediaWiki installation directory.${BITNAMI_ROOT_DIR}/mediawiki
MEDIAWIKI_CONF_FILEConfiguration file for MediaWiki.${MEDIAWIKI_BASE_DIR}/LocalSettings.php
MEDIAWIKI_VOLUME_DIRMediaWiki directory for mounted configuration files.${BITNAMI_VOLUME_DIR}/mediawiki
PHP_DEFAULT_MEMORY_LIMITDefault PHP memory limit.256M

When you start the MediaWiki image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:

  • For docker-compose add the variable name and value under the application section in the docker-compose.yml file present in this repository:
mediawiki:
  ...
  environment:
    - MEDIAWIKI_PASSWORD=my_password
  ...
  • For manual execution add a --env option with each variable and value:

    docker run -d --name mediawiki -p 80:8080 -p 443:8443 \
      --env MEDIAWIKI_PASSWORD=my_password \
      --network mediawiki-tier \
      --volume /path/to/mediawiki-persistence:/bitnami/mediawiki \
      bitnami/mediawiki:latest
    

Example

This would be an example of SMTP configuration using a GMail account:

  mediawiki:
    ...
    environment:
      - MEDIAWIKI_DATABASE_USER=bn_mediawiki
      - MEDIAWIKI_DATABASE_NAME=bitnami_mediawiki
      - ALLOW_EMPTY_PASSWORD=yes
      - MEDIAWIKI_SMTP_HOST=smtp.gmail.com
      - MEDIAWIKI_SMTP_HOST_ID=mydomain.com
      - MEDIAWIKI_SMTP_PORT=587
      - MEDIAWIKI_SMTP_USER=your_email@gmail.com
      - MEDIAWIKI_SMTP_PASSWORD=your_password
  ...
  • For manual execution:

    docker run -d --name mediawiki -p 80:8080 -p 443:8443 \
      --env MEDIAWIKI_DATABASE_USER=bn_mediawiki \
      --env MEDIAWIKI_DATABASE_NAME=bitnami_mediawiki \
      --env MEDIAWIKI_SMTP_HOST=smtp.gmail.com \
      --env MEDIAWIKI_SMTP_HOST_ID=mydomain.com \
      --env MEDIAWIKI_SMTP_PORT=587 \
      --env MEDIAWIKI_SMTP_USER=your_email@gmail.com \
      --env MEDIAWIKI_SMTP_PASSWORD=your_password \
      --network mediawiki-tier \
      --volume /path/to/mediawiki-persistence:/bitnami/mediawiki \
      bitnami/mediawiki:latest
    

How to install imagemagick in the Bitnami MediaWiki Docker image

If you require better quality thumbnails for your uploaded images, you may want to install imagemagick instead of using GD. To do so you can build your own docker image adding the imagemagick system package. Since we are using a non-root container, we have to swap the user to root to install imagemagick and it's requirements.

  1. Create the following Dockerfile

    FROM bitnami/mediawiki:latest
    USER root
    RUN install_packages imagemagick
    USER 1001
    
  2. Build the docker image

    docker build -t bitnami/mediawiki:imagemagick .
    
  3. Edit the docker-compose.yml to use the docker image built in the previous step.

  4. Finally exec into your MediaWiki container and edit the file /opt/bitnami/mediawiki/LocalSettings.php as described here in order to start using imagemagick.

How to migrate from a Bitnami MediaWiki Stack

You can follow these steps in order to migrate it to this container:

  1. Export the data from your SOURCE installation: (assuming an installation in /opt/bitnami directory)

    mysqldump -u root -p bitnami_mediawiki > ~/backup-mediawiki-database.sql
    gzip -c ~/backup-mediawiki-database.sql > ~/backup-mediawiki-database.sql.gz
    cd /opt/bitnami/apps/mediawiki/htdocs/
    tar cfz ~/backup-mediawiki-extensions.tar.gz extensions
    tar cfz ~/backup-mediawiki-images.tar.gz images
    tar cfz ~/backup-mediawiki-skins.tar.gz skins
    
  2. Copy the backup files to your TARGET installation:

    scp ~/backup-mediawiki-* YOUR_USERNAME@TARGET_HOST:~
    
  3. Create the MediaWiki Container as described in the section How to use this Image (Using Docker Compose)

  4. Wait for the initial setup to finish. You can follow it with

    docker-compose logs -f mediawiki
    

    and press Ctrl-C when you see this:

    nami    INFO  mediawiki successfully initialized
    Starting mediawiki ...
    
  5. Stop Apache:

    docker-compose exec mediawiki nami stop apache
    
  6. Obtain the password used by MediaWiki to access the database in order avoid reconfiguring it:

    docker-compose exec mediawiki bash -c 'cat /opt/bitnami/mediawiki/LocalSettings.php | grep wgDBpassword'
    
  7. Restore the database backup: (replace ROOT_PASSWORD below with your MariaDB root password)

    cd ~
    docker-compose exec mariadb mysql -u root -pROOT_PASSWORD
    MariaDB [(none)]> drop database bitnami_mediawiki;
    MariaDB [(none)]> create database bitnami_mediawiki;
    MariaDB [(none)]> grant all privileges on bitnami_mediawiki.* to 'bn_mediawiki'@'%' identified by 'PASSWORD_OBTAINED_IN_STEP_6';
    MariaDB [(none)]> exit
    gunzip -c ./backup-mediawiki-database.sql.gz | docker exec -i $(docker-compose ps -q mariadb) mysql -u root bitnami_mediawiki -pROOT_PASSWORD
    
  8. Restore extensions/images/skins directories from backup:

    cat ./backup-mediawiki-extensions.tar.gz | docker exec -i $(docker-compose ps -q mediawiki) bash -c 'cd /bitnami/mediawiki/ ; tar -xzvf -'
    cat ./backup-mediawiki-images.tar.gz | docker exec -i $(docker-compose ps -q mediawiki) bash -c 'cd /bitnami/mediawiki/ ; tar -xzvf -'
    cat ./backup-mediawiki-skins.tar.gz | docker exec -i $(docker-compose ps -q mediawiki) bash -c 'cd /bitnami/mediawiki/ ; tar -xzvf -'
    
  9. Fix MediaWiki directory permissions:

    docker-compose exec mediawiki chown -R daemon:daemon /bitnami/mediawiki
    
  10. Restart Apache:

    docker-compose exec mediawiki nami start apache
    

Logging

The Bitnami MediaWiki Docker image sends the container logs to stdout. To view the logs:

docker logs mediawiki

Or using Docker Compose:

docker-compose logs mediawiki

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

Maintenance

Backing up your container

To backup your data, configuration and logs, follow these simple steps:

Step 1: Stop the currently running container

docker stop mediawiki

Or using Docker Compose:

docker-compose stop mediawiki

Note: the README for this image is longer than the DockerHub length limit of 25000, so has been trimmed. The full README can be found at https://github.com/bitnami/containers/blob/main/bitnami/mediawiki/README.md

Docker Pull Command

docker pull bitnami/mediawiki
Bitnami