first run default compose: Unable to start com.bitnami.mariadb: Cannot find pid file about bitnami-docker-moodle HOT 6 CLOSED

seems to lack of RAM problem and OOM killer killing something accidentally. VM Configuration is a 512Mb RAM, But when I change it to 2Gb RAM started compose (mariadb+moodle) occupied 1200 Mb RAM.. :)))
Started Normally, But you need to mention it in readme ....

from bitnami-docker-moodle.

The nami initialize command for Moodle is probably loading webkit to work its way through the setup wizard. I've noticed that this can take a allocate a lot of the available RAM. Take into account that this high memory allocation only occurs at the first launch, subsequent application launches will probably be fine on 512MB systems.

But I agree, it's probably a good idea to have the minimum requirements listed. We'll discuss it internally trying to figure out the best option.

from bitnami-docker-moodle.

But my cloud provider has a different hosting plans and support upgrades, but only to higher plans.
1: 512Mb RAM - $4/month 2: 2Gb RAM - $16/month
Then I must go to plan/VM 2 for first run, but I cannot degrade to plan 1 for subsequent runs and forced to pay $16/month, although this is no longer necessary.

from bitnami-docker-moodle.

@combrs Ideally a 1GB instance should be a good choice to run moodle and you should also not see this issue. Does your hosting provider not offer an instance type with 1Gb of system memory?

Also could you try starting the mariadb instance first and once its fully started start the moodle container. The README should have instructions to run these containers using the docker cli.

Do let us know

from bitnami-docker-moodle.

@sameersbn Yes, on 1Gb machine that default installation start OK without errors.

from bitnami-docker-moodle.

Thats great! I believe you should use the 1GB instance.

from bitnami-docker-moodle.