Skip to content

Instantly share code, notes, and snippets.

@dnburgess
Last active August 6, 2024 12:49
Show Gist options
  • Save dnburgess/a1bf8835f699123987cca2fcdec14f37 to your computer and use it in GitHub Desktop.
Save dnburgess/a1bf8835f699123987cca2fcdec14f37 to your computer and use it in GitHub Desktop.
DB Tech Moodle
version: '2'
services:
mariadb:
image: mariadb
volumes:
- /srv/Configs/Databases/Moodle:/var/lib/mysql
environment:
- MYSQL_ROOT_PASSWORD=moodle
- MYSQL_ROOT_USER=root
- MYSQL_DATABASE=moodle
moodle:
image: bitnami/moodle:latest
ports:
- 8080:8080
- 8443:8443
environment:
- MOODLE_DATABASE_HOST=mariadb
- MOODLE_DATABASE_USER=root
- MOODLE_DATABASE_PASSWORD=moodle
- MOODLE_DATABASE_NAME=moodle
- PUID=998
- PGID=100
volumes:
- /srv/Configs/Moodle:/bitnami/moodle
- /srv/Configs/MoodleData:/bitnami/moodledata
depends_on:
- mariadb
links:
- mariadb:mariadb
@zeemalik2008
Copy link

Sir, i have already a same port for NGINX , what i can do with this compose,

here is my NGINX stack details .

version: '2'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
ports:
- '80:80'
- '81:81'
- '443:443'
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: “npm”
DB_MYSQL_NAME: "npm"
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
db:
image: 'jc21/mariadb-aria:latest'
environment:
MYSQL_ROOT_PASSWORD: ’npm’
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: ’npm’
volumes:
- ./data/mysql:/var/lib/mysql

@blUeBUg200
Copy link

blUeBUg200 commented Apr 2, 2023

@zeemalik2008 configure different ports in your compose file,

Example,

ports:
- '4040:80'
- '4041:81'
- '8443:443'

@IMAG0D
Copy link

IMAG0D commented Jun 6, 2023

Hey is there an ENV variable I can pass to alter the default server timezone. The usual docker convention TZ='time/zone' isnt working for me

@kiddyyang
Copy link

Hello Sir,

I saw your video on YouTube and I want to thank you for your guidance. I encountered the same issue when using the official Docker Compose file.

Everything worked fine when I previously used your Docker Compose file, but due to data loss from our VPS provider, we now need to redeploy. During this redeployment, I encountered a problem: the container unexpectedly exits whenever it reaches the "Running script" stage. Below are the logs. I would greatly appreciate it if you could take a look when you have time. Thank you very much!

moodle 17:46:38.27 INFO ==>
moodle 17:46:38.28 INFO ==> Welcome to the Bitnami moodle container
moodle 17:46:38.28 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
moodle 17:46:38.28 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
moodle 17:46:38.28 INFO ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
moodle 17:46:38.28 INFO ==>
moodle 17:46:38.28 INFO ==> ** Starting Moodle setup **
moodle 17:46:38.29 INFO ==> Generating sample certificates
Certificate request self-signature ok
subject=CN = example.com
realpath: /bitnami/apache/conf: No such file or directory
moodle 17:46:39.48 INFO ==> Configuring Apache ServerTokens directive
moodle 17:46:39.49 INFO ==> Configuring PHP options
moodle 17:46:39.50 INFO ==> Setting PHP expose_php option
moodle 17:46:39.50 INFO ==> Setting PHP output_buffering option
moodle 17:46:39.51 INFO ==> Validating settings in MYSQL_CLIENT_* env vars
moodle 17:46:39.52 INFO ==> Validating settings in POSTGRESQL_CLIENT_* env vars
moodle 17:46:39.59 INFO ==> Ensuring Moodle directories exist
moodle 17:46:39.61 INFO ==> Trying to connect to the database server
moodle 17:46:59.67 INFO ==> Running Moodle install script

@circleconsult-mk
Copy link

Hello Sir,

I saw your video on YouTube and I want to thank you for your guidance. I encountered the same issue when using the official Docker Compose file.

Everything worked fine when I previously used your Docker Compose file, but due to data loss from our VPS provider, we now need to redeploy. During this redeployment, I encountered a problem: the container unexpectedly exits whenever it reaches the "Running script" stage. Below are the logs. I would greatly appreciate it if you could take a look when you have time. Thank you very much!

moodle 17:46:38.27 INFO ==> moodle 17:46:38.28 INFO ==> Welcome to the Bitnami moodle container moodle 17:46:38.28 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers moodle 17:46:38.28 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues moodle 17:46:38.28 INFO ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise moodle 17:46:38.28 INFO ==> moodle 17:46:38.28 INFO ==> ** Starting Moodle setup ** moodle 17:46:38.29 INFO ==> Generating sample certificates Certificate request self-signature ok subject=CN = example.com realpath: /bitnami/apache/conf: No such file or directory moodle 17:46:39.48 INFO ==> Configuring Apache ServerTokens directive moodle 17:46:39.49 INFO ==> Configuring PHP options moodle 17:46:39.50 INFO ==> Setting PHP expose_php option moodle 17:46:39.50 INFO ==> Setting PHP output_buffering option moodle 17:46:39.51 INFO ==> Validating settings in MYSQL_CLIENT_* env vars moodle 17:46:39.52 INFO ==> Validating settings in POSTGRESQL_CLIENT_* env vars moodle 17:46:39.59 INFO ==> Ensuring Moodle directories exist moodle 17:46:39.61 INFO ==> Trying to connect to the database server moodle 17:46:59.67 INFO ==> Running Moodle install script

Did you find a solution?

@kiddyyang
Copy link

Hello Sir,
I saw your video on YouTube and I want to thank you for your guidance. I encountered the same issue when using the official Docker Compose file.
Everything worked fine when I previously used your Docker Compose file, but due to data loss from our VPS provider, we now need to redeploy. During this redeployment, I encountered a problem: the container unexpectedly exits whenever it reaches the "Running script" stage. Below are the logs. I would greatly appreciate it if you could take a look when you have time. Thank you very much!

moodle 17:46:38.27 INFO ==> moodle 17:46:38.28 INFO ==> Welcome to the Bitnami moodle container moodle 17:46:38.28 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers moodle 17:46:38.28 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues moodle 17:46:38.28 INFO ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise moodle 17:46:38.28 INFO ==> moodle 17:46:38.28 INFO ==> ** Starting Moodle setup ** moodle 17:46:38.29 INFO ==> Generating sample certificates Certificate request self-signature ok subject=CN = example.com realpath: /bitnami/apache/conf: No such file or directory moodle 17:46:39.48 INFO ==> Configuring Apache ServerTokens directive moodle 17:46:39.49 INFO ==> Configuring PHP options moodle 17:46:39.50 INFO ==> Setting PHP expose_php option moodle 17:46:39.50 INFO ==> Setting PHP output_buffering option moodle 17:46:39.51 INFO ==> Validating settings in MYSQL_CLIENT_* env vars moodle 17:46:39.52 INFO ==> Validating settings in POSTGRESQL_CLIENT_* env vars moodle 17:46:39.59 INFO ==> Ensuring Moodle directories exist moodle 17:46:39.61 INFO ==> Trying to connect to the database server moodle 17:46:59.67 INFO ==> Running Moodle install script

Did you find a solution?

Yes, I used the official Docker Compose file and granted the necessary permissions for some files. Finally, it works.
Thank you for your reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment