bitnami/moodle
Bitnami container image for Bitnami LMS powered by Moodle™ LMS
10M+
Moodle™ LMS is an open source online Learning Management System widely used at universities, schools, and corporations. It is modular and highly adaptable to any type of online learning.
Overview of Bitnami LMS powered by Moodle™ LMS Disclaimer: The respective trademarks mentioned in the offering are owned by the respective companies. We do not provide commercial license of any of these products. This listing has an open source license. Moodle(TM) LMS is run and maintained by Moodle HQ, that is a completely and separate project from Bitnami.
docker run --name moodle bitnami/moodle: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 deployment.
Looking to use Bitnami LMS powered by Moodle™ LMS in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.
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 Chart for Moodle™ GitHub repository.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
Starting December 10th 2024, only the latest stable branch of any container will receive updates in the free Bitnami catalog. To access up-to-date releases for all upstream-supported branches, consider upgrading to Bitnami Premium. Previous versions already released will not be deleted. They are still available to pull from DockerHub.
Please check the Bitnami Premium page in our partner Arrow Electronics for more information.
Dockerfile
linksLearn 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.
The recommended way to get the Bitnami Docker Image for Moodle™ is to pull the prebuilt image from the Docker Hub Registry.
docker pull bitnami/moodle: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/moodle:[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 .
Moodle™ requires access to a MySQL or MariaDB database to store information. We'll use the Bitnami Docker Image for MariaDB for the database requirements.
Step 1: Create a network
docker network create moodle-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_moodle \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_moodle \
--network moodle-network \
--volume mariadb_data:/bitnami/mariadb \
bitnami/mariadb:latest
Step 3: Create volumes for Moodle™ persistence and launch the container
$ docker volume create --name moodle_data
docker run -d --name moodle \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MOODLE_DATABASE_USER=bn_moodle \
--env MOODLE_DATABASE_PASSWORD=bitnami \
--env MOODLE_DATABASE_NAME=bitnami_moodle \
--network moodle-network \
--volume moodle_data:/bitnami/moodle \
--volume moodledata_data:/bitnami/moodledata \
bitnami/moodle:latest
Access your application at http://your-ip/
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/moodle/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.
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/moodle
path and another at /bitnami/moodledata
. 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, moodle_data and moodledata_data. The Moodle™ 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.
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
...
moodle:
...
volumes:
- - 'moodle_data:/bitnami/moodle'
+ - /path/to/moodle-persistence:/bitnami/moodle
- - 'moodledata_data:/bitnami/moodledata'
+ - /path/to/moodledata-persistence:/bitnami/moodle
...
-volumes:
- mariadb_data:
- driver: local
- moodle_data:
- driver: local
Step 1: Create a network (if it does not exist)
docker network create moodle-network
Step 2. Create a MariaDB container with host volume
docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_moodle \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_moodle \
--network moodle-network \
--volume /path/to/mariadb-persistence:/bitnami/mariadb \
bitnami/mariadb:latest
Step 3. Create the Moodle™ container with host volumes
docker run -d --name moodle \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MOODLE_DATABASE_USER=bn_moodle \
--env MOODLE_DATABASE_PASSWORD=bitnami \
--env MOODLE_DATABASE_NAME=bitnami_moodle \
--network moodle-network \
--volume /path/to/moodle-persistence:/bitnami/moodle \
--volume /path/to/moodledata-persistence:/bitnami/moodledata \
bitnami/moodle:latest
Customizable environment variables
Name | Description | Default Value |
---|---|---|
MOODLE_DATA_DIR | Directory where to store Moodle data files. | ${BITNAMI_VOLUME_DIR}/moodledata |
MOODLE_DATA_TO_PERSIST | Files to persist relative to the Moodle installation directory. To provide multiple values, separate them with a whitespace. | $MOODLE_BASE_DIR |
MOODLE_SKIP_BOOTSTRAP | Whether to perform initial bootstrapping for the application. | nil |
MOODLE_INSTALL_EXTRA_ARGS | Extra arguments to pass to the Moodle install.php script. | nil |
MOODLE_SITE_NAME | Moodle site name. | New Site |
MOODLE_HOST | Moodle www root. | nil |
MOODLE_CRON_MINUTES | Moodle cron frequency in minutes. | 1 |
MOODLE_REVERSEPROXY | Activate the reverseproxy feature of Moodle. | no |
MOODLE_SSLPROXY | Activate the sslproxy feature of Moodle. | no |
MOODLE_LANG | Allow to define default site language | en |
MOODLE_USERNAME | Moodle user name. | user |
MOODLE_PASSWORD | Moodle user password. | bitnami |
MOODLE_DATABASE_MIN_VERSION | Change database minimum version because of an issue with Azure Database for MariaDB. | nil |
MOODLE_EMAIL | Moodle user e-mail address. | user@example.com |
MOODLE_SMTP_HOST | Moodle SMTP server host. | nil |
MOODLE_SMTP_PORT_NUMBER | Moodle SMTP server port number. | nil |
MOODLE_SMTP_USER | Moodle SMTP server user. | nil |
MOODLE_SMTP_PASSWORD | Moodle SMTP server user password. | nil |
MOODLE_SMTP_PROTOCOL | Moodle SMTP server protocol. | nil |
MOODLE_DATABASE_TYPE | Database type to be used for the Moodle installation. | mariadb |
MOODLE_DATABASE_HOST | Database server host. | mariadb |
MOODLE_DATABASE_PORT_NUMBER | Database server port. | 3306 |
MOODLE_DATABASE_NAME | Database name. | bitnami_moodle |
MOODLE_DATABASE_USER | Database user name. | bn_moodle |
MOODLE_DATABASE_PASSWORD | Database user password. | nil |
Read-only environment variables
Name | Description | Value |
---|---|---|
MOODLE_BASE_DIR | Moodle installation directory. | ${BITNAMI_ROOT_DIR}/moodle |
MOODLE_CONF_FILE | Configuration file for Moodle. | ${MOODLE_BASE_DIR}/config.php |
MOODLE_VOLUME_DIR | Persisted directory for Moodle files. | ${BITNAMI_VOLUME_DIR}/moodle |
PHP_DEFAULT_MEMORY_LIMIT | Default PHP memory limit. | 256M |
PHP_DEFAULT_MAX_INPUT_VARS | Default maximum amount of input variables for PHP scripts. | 5000 |
When you start the Moodle™ 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:
docker-compose.yml
file present in this repository:moodle:
...
environment:
- MOODLE_PASSWORD=my_password
...
For manual execution add a --env
option with each variable and value:
docker run -d --name moodle -p 80:8080 -p 443:8443 \
--env MOODLE_PASSWORD=my_password \
--network moodle-tier \
--volume /path/to/moodle-persistence:/bitnami/moodle \
--volume /path/to/moodledata-persistence:/bitnami/moodledata \
bitnami/moodle:latest
This would be an example of SMTP configuration using a Gmail account:
Modify the docker-compose.yml
file present in this repository:
moodle:
...
environment:
- MOODLE_DATABASE_USER=bn_moodle
- MOODLE_DATABASE_NAME=bitnami_moodle
- ALLOW_EMPTY_PASSWORD=yes
- MOODLE_SMTP_HOST=smtp.gmail.com
- MOODLE_SMTP_PORT=587
- MOODLE_SMTP_USER=your_email@gmail.com
- MOODLE_SMTP_PASSWORD=your_password
- MOODLE_SMTP_PROTOCOL=tls
...
For manual execution:
docker run -d --name moodle -p 80:8080 -p 443:8443 \
--env MOODLE_DATABASE_USER=bn_moodle \
--env MOODLE_DATABASE_NAME=bitnami_moodle \
--env MOODLE_SMTP_HOST=smtp.gmail.com \
--env MOODLE_SMTP_PORT=587 \
--env MOODLE_SMTP_USER=your_email@gmail.com \
--env MOODLE_SMTP_PASSWORD=your_password \
--env MOODLE_SMTP_PROTOCOL=tls \
--network moodle-tier \
--volume /path/to/moodle-persistence:/bitnami/moodle \
--volume /path/to/moodledata-persistence:/bitnami/moodledata \
bitnami/moodle:latest
This would be an instance ready to be put behind the NGINX load balancer.
Modify the docker-compose.yml
file present in this repository:
moodle:
...
environment:
- MOODLE_HOST=example.com
- MOODLE_REVERSEPROXY=true
- MOODLE_SSLPROXY=true
...
For manual execution:
docker run -d --name moodle -p 80:8080 -p 443:8443 \
--env MOODLE_HOST=example.com \
--env MOODLE_REVERSEPROXY=true \
--env MOODLE_SSLPROXY=true \
--network moodle-tier \
--volume /path/to/moodle-persistence:/bitnami/moodle \
--volume /path/to/moodledata-persistence:/bitnami/moodledata \
bitnami/moodle:latest
By default, this container packs a generic English version of Moodle™. Nevertheless, more Language Packs can be added to the default configuration using the in-platform Administration interface. In order to fully support a new Language Pack it is also a requirement to update the system's locales files. To do that, you have several options:
Build the default image with the EXTRA_LOCALES
build-time variable
You can add extra locales using the EXTRA_LOCALES
build-time variable when building the Docker image. The values must be separated by commas or semicolons (and optional spaces), and refer to entries in the /usr/share/i18n/SUPPORTED
file inside the container.
For example, the following value would add French, German, Italian and Spanish, you would specify the following value in EXTRA_LOCALES
:
fr_FR.UTF-8 UTF-8, de_DE.UTF-8 UTF-8, it_IT.UTF-8 UTF-8, es_ES.UTF-8 UTF-8
NOTE: The locales
en_AU.UTF-8 UTF-8
anden_US.UTF-8 UTF-8
will always be packaged, defaulting toen_US.UTF-8 UTF-8
.
To use EXTRA_LOCALES
, you have two options:
Modify the docker-compose.yml
file present in this repository:
moodle:
...
# image: 'bitnami/moodle:latest' # remove this line !
build:
context: .
dockerfile: Dockerfile
args:
- EXTRA_LOCALES=fr_FR.UTF-8 UTF-8, de_DE.UTF-8 UTF-8, it_IT.UTF-8 UTF-8, es_ES.UTF-8 UTF-8
...
For manual execution, clone the repository and run the following command inside the X/debian-12
directory:
docker build -t bitnami/moodle:latest --build-arg EXTRA_LOCALES="fr_FR.UTF-8 UTF-8, de_DE.UTF-8 UTF-8, it_IT.UTF-8 UTF-8, es_ES.UTF-8 UTF-8" .
Enable all supported locales using the WITH_ALL_LOCALES
build-time variable
You can generate all supported locales by setting the build environment variable WITH_ALL_LOCALES=yes
. Note that the generation of all the locales takes some time.
To use WITH_ALL_LOCALES
, you have two options:
Modify the docker-compose.yml
file present in this repository:
moodle:
...
# image: 'bitnami/moodle:latest' # remove this line !
build:
context: .
dockerfile: Dockerfile
args:
- WITH_ALL_LOCALES=yes
...
For manual execution, clone the repository and run the following command inside the X/debian-12
directory:
docker build -t bitnami/moodle:latest --build-arg WITH_ALL_LOCALES=yes .
Extending the default image
Finally, you can extend the default image and adding as many locales as needed:
FROM bitnami/moodle
RUN echo "es_ES.UTF-8 UTF-8" >> /etc/locale.gen && locale-gen
Bear in mind that in the example above es_ES.UTF-8 UTF-8
is the locale needed for the desired Language Pack to install. You may change this value to the locale corresponding to your pack.
The Bitnami Docker image for Moodle™ sends the container logs to stdout
. To view the logs:
docker logs moodle
Or using Docker Compose:
docker-compose logs moodle
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.
By default, the logging of debug information is disabled. You can enable it by setting the environment variable BITNAMI_DEBUG
to true
.
To backup your data, configuration and logs, follow these simple steps:
Step 1: Stop the currently running container
docker stop moodle
Or using Docker Compose:
docker-compose stop moodle
Step 2: Run the backup command
We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
docker run --rm -v /path/to/moodle-backups:/backups --volumes-from moodle busybox \
cp -a /bitnami/moodle /backups/latest
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the MariaDB database container:
$ docker run -d --name mariadb \
...
- --volume /path/to/mariadb-persistence:/bitnami/mariadb \
+ --volume /path/to/mariadb-backups/latest:/bitnami/mariadb \
bitnami/mariadb:latest
For the Moodle™ container:
$ docker run -d --name moodle \
...
- --volume /path/to/moodle-persistence:/bitnami/moodle \
+ --volume /path/to/moodle-backups/latest/moodle:/bitnami/moodle \
- --volume /path/to/moodledata-persistence:/bitnami/moodledata \
+ --volume /path/to/moodledata-backups/latest/moodledata:/bitnami/moodledata \
bitnami/moodle:latest
NOTE: Since Moodle(TM) 3.4.0-r1, the application upgrades should be done manually inside the docker container following the official documentation. As an alternative, you can try upgrading using an updated Docker image. However, any data from the Moodle(TM) container will be lost and you will have to reinstall all the plugins and themes you manually added.
Bitnami provides up-to-date versions of MariaDB and Moodle™, including security patches, soon after they are made up
Note: the README for this container is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://github.com/bitnami/containers/blob/main/bitnami/moodle/README.md