Howard Miller

If it helps, here is the Docker setup I use for dev - https://github.com/thepurpleblob/DockerMoodle

It has nginx and php-fpm in separate containers. Actually two - one for the web and one for cron.

Please note!! This was not intended to be shared, and the notes are mostly for me for when I forgot what I did. So please tread carefully.

Indeed - I have no requirement to do that. I have no idea how to deploy Docker in large / high-availability environments. I'm assuming that's where things like Kubernetes come into play - but that's far outside of my experience.

The problem is that you are, in effect, writing your own, dreaded, one-click installer for Moodle. So they question becomes, "Docker environment to do what?".

My approach was to look at tutorials for building a basic LAMP stack in Docker and extrapolating from there.

I'm very late to the party - but if this is just for testing, run the database in a Docker container? Then you can have any version you like, more or less.

I very much doubt that this is related to the version of Moodle. The database layer doesn't change much.

Firstly, turn on Debugging and get the full trace when you get that error. What is the database doing when it fails ('show processlist' at the very least)?