I figured this out an am logging this for future Portainer Moodle sys admins.
Bottom line up front (BLUF): I wanted to update my Moodle site that is running in a portainer instances following DB Tech's tutorial on the process. The issue I was having was that when I tried to re-deploy or upgrade the Bitnami instance, It would not work unless I did a complete wipe. I tried everything from messing with portainer, bash commands, etc. Nothing worked. What finally worked for me was the following.
First: Download the new 4.3+ version tar, and upload that tar to the server hosting your portainer instance, for me it was Turnkey Linux webmin, following the Moodle documentation and a video from "radio puust" on YouTube showed a simple drag and drop/rename for the upgrade that was super easy to follow.
Second: Now you have to migrate over all the files by dragging and dropping them from your backup file. For me it was Moodle.backup, these files include the config, badges, etc. The youtube video titled "Upgrading your current Moodle site to Moodle 4.x" covers this.
Third: Now after you have done this, restart the containers... monitor the logs in portainer, you will think the moodle front facing container is hanging because of the " moodle 14:52:17.72 INFO ==> Running database upgrade " what i did to fix this was by restarting the database and letting it start fully since i have it in a separate container, once the logs shows that was booted I then restart the moodle front facing site and it presented the same loop "moodle 14:52:17.72 INFO ==> Running database upgrade" So i waited and waited while re searching, about 30 mins, and it finally started and i am able to log in.
Lastly, go to notifications and look at " you have plugins that need updates" .... I saw HPV5 needs update, I unstalled it... Now It went and allowed me to do the install process.
Finally :
by fly gav. Your Moodle code is up-to-date!