-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/moodle] Moodle won't start "grep: /opt/bitnami/moodle/config.php: No such file or directory" #74719
Comments
I get a similar error when trying to mount two mods like so volumes:
- moodle_data:/bitnami/moodle
- moodledata_data:/bitnami/moodledata
- ./mods/grouptool:/bitnami/moodle/mod/grouptool
- ./mods/organizer:/bitnami/moodle/mod/organizer |
Hi, Bind-mounting volumes in a non-root container is a bit problematic. Could you ensure that the initial installation script gets run? I would try ensuring that the volumes |
Thank you, I solved my problem using docker cp instead. |
Yes I've checked the both those volumes are empty. Ownership for the folders is to 1001 too. Full logs for moodle container (which exits with code 2) are:
MariaDB logs:
After running the MariaDB folders have plenty of files added, the Moodle and Moodle Data both remain empty. |
Hi, I see this line
That mean that the installation logic is assuming that Moodle has already been initialized despite the installation not being ready. I imagine this has to do the extra plugins you are mounting. Let's try the following. Could you please first try an installation with the empty volumes but without the modules, and then, once it's been initialized, try mounting the extra modules? |
Thanks for the reply @javsalgar - I wasn't aware I was mounting any extra modules - I couldn't see any in the docker compose? I agree it did seem a bit weird re the message about a persisted installation, I don't know where it could be getting that from? I've also done a |
Name and Version
bitnami/moodle4.5
What architecture are you using?
amd64
What steps will reproduce the bug?
What is the expected behavior?
Containers start and run OK
What do you see instead?
Initially I couldn't get mariadb to work but then read elsewhere that it needs PGID/PUID of 1001 so created a user with that and did a
chown
for the mariadb folders. It now starts fine.The main Moodle container boots but then has an issue - see debug logs below. It just keeps restarting. I also note that nothing is written to the mounted volumes (compared to the mariadb ones). I've down the same
chown
for the moodle folders too.Additional information
Portainer stack/Docker compose:
mariadb container logs:
moodle container logs:
The text was updated successfully, but these errors were encountered: