ellakcy / moodle-compose Goto Github PK

Hi,

closely related to #4 I am facing the very same issue running master:

#[...]
moodle_1     | webservice/xmlrpc/tests/fixtures/array_response.xml
moodle_1     | webservice/xmlrpc/tests/fixtures/fault_response.xml
moodle_1     | webservice/xmlrpc/tests/fixtures/value_response.xml
moodle_1     | 
moodle_1     | sent 201,859,228 bytes  received 415,347 bytes  527,443.48 bytes/sec
moodle_1     | total size is 200,314,964  speedup is 0.99
moodle_1     | Fixing files and permissions
moodle_1     | Installing moodle with  support
moodle_1     | No database support found
moodle_moodle_1 exited with code 1

I've been trying to get it work based on your suggestion in #4 using image: ellakcy/moodle:postgresql_apache_38 but it brings no change whatsoever (master currently features image: ellakcy/moodle:postgresql_apache).

I've also tried mysql, mariadb and postgres, all of them show the very same issue, any idea what I can try?

Thanks!

currently using the following version

ellakcy/moodle:postgresql_apache_latest

please see below logs:

sent 190,244,901 bytes received 409,147 bytes 22,429,888.00 bytes/sec
total size is 230,933,412 speedup is 1.21
Fixing files and permissions
Installing moodle with pgsql support
No database support found

I am trying to setup the apache_mysql variant, containers get created and stuff initialized, but moodle container can't seem to create the database, exits with the error:

No database support found

.env is setup using the dist file (just swapped the values need swapping). Am I missing something?

currently using the following version

ellakcy/moodle:postgresql__apache_38

please see below logs:

Fixing files and permissions
Installing moodle with support
No database support found

Over my .env I have setup the following settings

# In case of a reverse proxy please change the following setting
# It should have the url that the USER provides into her/his browser.

MOODLE_URL=https://example.com

# Database configuration
MOODLE_DB_USER=moodle
MOODLE_DB_PASSWORD=somepasswd
MOODLE_DB_NAME=moodle

# Default user
MOODLE_ADMIN=admin
MOODLE_ADMIN_PASSWORD=admin
MOODLE_ADMIN_EMAIL=fakepasswd

# Indicate whethers runs Behind SSL Proxy (set values in true  by default are set as false)
MOODLE_REVERSE_LB="true"
MOODLE_SSL="true"

#mail settings
MOODLE_EMAIL_TYPE_QMAIL=false # Set true is qmail MTA a used
MOODLE_EMAIL_HOST=mail.example.com

But for some reason I get a 303 redirect loop, therefore the browser fails to load the moodle. How I can fix that?

hello,

trying to get moodle running with your docker-compose setup (which looks very nice, thanks!).

i'm having trouble with the apache-postgres setup and am noticing this error in the logs. not sure if it's just a warning or an error, but thought i'd report it:

moodle             | == Environment ==
moodle             | !! database postgres (9.6.24) !!
moodle             | [System] version 10 is required and you are running 9.6.24 -
moodle             |

Hello,

I'm trying to use your docker-compose file to run a Moodle instance with Nginx and PostgreSQL on Ubuntu 18.04. I'm getting the following error when running docker-compose up -d:

root@educationexperience:~/dockercompose/moodle-compose# docker-compose up -d
WARNING: The moodle variable is not set. Defaulting to a blank string.
WARNING: The guintera_mdluser variable is not set. Defaulting to a blank string.
WARNING: The lnxr0x variable is not set. Defaulting to a blank string.
Starting moodle-compose_moodle_db_1 ... done
Starting moodle-compose_moodle_1 ... error

ERROR: for moodle-compose_moodle_1 Cannot start service moodle: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: "/usr/local/bin/entrypoint.sh": permission denied": unknown

ERROR: for moodle Cannot start service moodle: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: "/usr/local/bin/entrypoint.sh": permission denied": unknown
ERROR: Encountered errors while bringing up the project.

I tried to locate the entrypoint.sh file to that I could fix this apparent permission error, but I was unable to find it. I searched on google and similar errors are permission related, but some tinkering on the Dockerfile is necessary, which I was not able to find either. Could you give me a hint on solving this issue?

Thanks in advance and thank you for the great work in this github project. 

regards,

• Breno