Pardon 2 cents worth ...
Noticed in your screen shots you acquire the moodle code via git and then remove the hidden .git directory ... which means you loose the ability to acquire point releases - maybe even 0 day flaws (happened only once in many years, but still ...)
You also loose the ability to upgrade the site as long as server has compat versions of PHP + extensions and DB version in place without the need of a new docker.
https://moodledev.io/general/releases
Yes, Docker gets AMP stack and a moodle setup quickly ... but doesn't that kinda limit you to above the water line with the moodle?
Often wondered ... so I'll ask a non-docker user stupid question ... how does that setup handle updates/upgrades to PHP/DB server/Web server?
There are things that need to be setup outside of moodle once it's up and running ... cron job. Maybe you could include in your docker a bash shell script to do a site backup?
For that matter, if one left .git, 2 more scripts ... one to update code for a point release ... and another to upgrade site when a desired higher version is released.
'SoS', Ken