readystack/moodle repository overview

⁠Moodle

readystack/moodle:v5.2.3-CE-debian-bookworm-r2

A hardened, cosign-signed, offline-rebuildable build of github.com/moodle/moodle v5.2.3 (GPL-3.0-or-later), built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

• Docker Scout — re-checked daily; today's grade and the reason for it are at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key; verify with cosign verify --key https://readystack.dev/keys/cosign.pub --insecure-ignore-tlog=true readystack/moodle:v5.2.3-CE-debian-bookworm-r2.
• Built from source, non-root.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v5.2.3-CE-debian-bookworm-r2 — the release on sale at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is hermetically built, signed, attested, and supported under your ReadyStack agreement.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer patched or re-graded: move to the current release. A superseded release's build kit is available through support.

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/moodle:v5.2.3-CE-debian-bookworm-r2

# ✗ unsupported (do not pull)
docker pull readystack/moodle:internal-...

Each release tag is signed; verify with cosign verify --key https://readystack.dev/keys/cosign.pub --insecure-ignore-tlog=true readystack/moodle:v5.2.3-CE-debian-bookworm-r2 (ReadyStack keeps signatures off the public transparency log, so the check is key-only). Support: [email protected]⁠.

⁠Deployment

Single container (Apache + mod_php, one foreground process) running the Moodle LMS. It REQUIRES an EXTERNAL MySQL 8.4+ / MariaDB 10.11+ database the operator provisions and points the container at via DB_HOST/DB_PORT/DB_NAME/DB_USER/DB_PASS — there is NO embedded/SQLite database. On first start Moodle runs php admin/cli/install.php to create config.php + all module schema (a multi-minute one-time install). NOT a multi-service cluster, but NOT self-contained: a MySQL/MariaDB server is a hard external dependency, and moodledata + the DB must persist.

docker run -d --name moodle -p 8080:8080 -e MOODLE_WWWROOT=https://moodle.example.com -e DB_HOST=YOUR_DB_HOST -e DB_PORT=3306 -e DB_NAME=moodle -e DB_USER=moodle -e DB_PASS=YOUR_DB_PW -e MOODLE_ADMIN_PASS=YOUR_STRONG_PW -e [email protected] -v moodle-data:/var/www/moodledata readystack/moodle:v5.2.3-CE-debian-bookworm-r2

The empty 'moodle' database, created with utf8mb4 as its default character set, must exist on your server first; first boot creates the schema, taking a few minutes.

⁠The full ReadyStack Agent-ready Archive

The complete --network=none build kit to recreate this exact image yourself — plus admin/DB/API handbooks, seed data, a validated test suite, and signed provenance — is at readystack.dev/buy.html⁠.

— ReadyStack · readystack.dev