As per Bitnami-Docker-Moodle issue, #95 regarding the initial installation seems that have been fixed as Wesley Salazar reports and I can confirm.
But, I'm in the same problem loop again.
I'm trying to run a copy of my production Moodle installation locally by following the steps below.
I used this bitnami docker moodle image for my tests
Step1: I'm creating the MariaDB and Moodle containers by docker-compose file and everything works fine.
Step2: Trying to change the docker volumes with persistent folders locally and works with some page load delays.
Step3: Paste my moodle folder content (from my production env) into the moodle folder created by step 2 into this "data persistent" folder which I have already clear, set the "MOODLE_SKIP_INSTALL=yes" variable, change my config.php file in order to be connected to my local MySQL DB (not the containerised MariaDB) and bring the containers up again.
At this point, I realized that the structure is different and there is an init script running on Moodle Installation step which creates folders into moodle directory (even that I get the message "The installation wizard will be skipped and parameters for configuring the user account and SMTP credentials will be ignored.")
FYI: My productive moodle folder contains only .bitnamimeta,backup,conf,htdocs,licenses,moodledata folders and bnconfig and updateip files, but the script creates at least 50 more folders and 40 more files in there.
1. The connection with my dedicated local DB seems to work (mysql-c INFO MySQL server listening and working at 192.168.1.3:3306) but I can't log in with an existing user (confirmed that exists in this DB and the password is correct).
2. The home page can't be loaded correctly. Seems like PHP issue. The images are missing and some js scripts are failed to load.
My expectations from the moodle container image was to start the container by indicating the DB variables and the location of the moodledata directory by binding a local folder as volume and get the Moodle service up and running.