[bitnami/moodle] Release 5.1.3-debian-12-r9 (#92485)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-04-15 17:24:19 +02:00
committed by GitHub
parent 0c3ea11903
commit 3dc7672722
2 changed files with 12 additions and 75 deletions
+4 -4
View File
@@ -9,7 +9,7 @@ ARG TARGETARCH
ARG WITH_ALL_LOCALES="no"
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-08T19:59:47Z" \
org.opencontainers.image.created="2026-04-15T14:51:59Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/moodle/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/moodle" \
@@ -30,11 +30,11 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"render-template-1.0.9-164-linux-${OS_ARCH}-debian-12" \
"php-8.4.19-1-linux-${OS_ARCH}-debian-12" \
"php-8.4.20-2-linux-${OS_ARCH}-debian-12" \
"apache-2.4.66-1-linux-${OS_ARCH}-debian-12" \
"postgresql-client-14.22.0-0-linux-${OS_ARCH}-debian-12" \
"mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \
"libphp-8.4.19-0-linux-${OS_ARCH}-debian-12" \
"libphp-8.4.20-0-linux-${OS_ARCH}-debian-12" \
"moodle-5.1.3-1-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
@@ -67,7 +67,7 @@ ENV APACHE_HTTPS_PORT_NUMBER="" \
APACHE_HTTP_PORT_NUMBER="" \
APP_VERSION="5.1.3" \
BITNAMI_APP_NAME="moodle" \
IMAGE_REVISION="8" \
IMAGE_REVISION="9" \
LANG="en_US.UTF-8" \
LANGUAGE="en_US:en" \
LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \
+8 -71
View File
@@ -11,7 +11,13 @@ Disclaimer: The respective trademarks mentioned in the offering are owned by the
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](#environment-variables) section for a more secure deployment.
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/moodle/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/moodle/docker-compose.yml)
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](https://github.com/bitnami/charts/tree/main/bitnami/moodle).
## Why use Bitnami Secure Images?
@@ -101,8 +107,6 @@ The following tables list the main variables you can set.
| `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&trade; 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.
### Examples
#### SMTP configuration
@@ -169,74 +173,7 @@ The Bitnami Bitnami LMS powered by Moodle&trade; LMS Docker image from the [Bitn
## Logging
The Bitnami Docker image for Moodle&trade; sends the container logs to `stdout`. To view the logs:
```console
docker logs moodle
```
Or using Docker Compose:
```console
docker-compose logs moodle
```
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) 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`.
## Maintenance
### Backing up your container
To backup your data, configuration and logs, follow these simple steps:
#### Step 1: Stop the currently running container
```console
docker stop moodle
```
Or using Docker Compose:
```console
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.
```console
docker run --rm -v /path/to/moodle-backups:/backups --volumes-from moodle busybox \
cp -a /bitnami/moodle /backups/latest
```
### Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the MariaDB database container:
```diff
$ 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&trade; container:
```diff
$ 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
```
The Bitnami Bitnami LMS powered by Moodle&trade; LMS Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Customize this image