A Dockerfile that installs and runs the latest Moodle 3.3 stable, with external MySQL Database.
- latest - 3.3 stable
- v3.2 - 3.2 stable
- v3.1 - 3.1 stable
git clone https://github.com/jmhardison/docker-moodle cd docker-moodle docker build -t moodle .
When running locally or for a test deployment, use of localhost is acceptable.
To spawn a new instance of Moodle:
docker run -d --name DB -p 3306:3306 -e MYSQL_DATABASE=moodle -e MYSQL_ROOT_PASSWORD=moodle -e MYSQL_USER=moodle -e MYSQL_PASSWORD=moodle mysql docker run -d -P --name moodle --link DB:DB -e MOODLE_URL=http://localhost:8080 -p 8080:80 jhardison/moodle
You can visit the following URL in a browser to get started:
For a production deployment of moodle, use of a FQDN is advised. This FQDN should be created in DNS for resolution to your host. For example, if your internal DNS is company.com, you could leverage moodle.company.com and have that record resolve to the host running your moodle container. The moodle url would then be,
In the following steps, replace MOODLE_URL with your appropriate FQDN.
- Deploy With Docker
docker run -d --name DB -p 3306:3306 -e MYSQL_DATABASE=moodle -e MYSQL_ROOT_PASSWORD=moodle -e MYSQL_USER=moodle -e MYSQL_PASSWORD=moodle mysql docker run -d -P --name moodle --link DB:DB -e MOODLE_URL=http://moodle.company.com -p 80:80 jhardison/moodle
- Deploy with Docker Compose
Pull the latest source from GitHub:
git clone https://github.com/jmhardison/docker-moodle.git
moodle_variables.env file with your information. Please note that we are using v3 compose files, as a stop gap link env variable are manually filled since v3 no longer automatically fills those for use.
Once the environment file is filled in you may bring up the service with:
docker-compose up -d
The following aren't handled, considered, or need work:
- moodle cronjob (should be called from cron container)
- log handling (stdout?)
- email (does it even send?)