Xibo content reset after server reboot

I need help resolving an issue with loosing content once xibo server is rebooted.
I tried to stop and start the containers as written in the manual but after doing that i get the error below.

Fatal Error - sorry this shouldn’t happen. SQLSTATE[HY000] [1045] Access denied for user ‘cms’@‘172.18.0.4’ (using password: YES)

Can you confirm what operating system you have installed your Docker setup on and which version of Docker you are using?

Can you also confirm if you have been using the docker-compose.yml or a custom yml file for your Docker setup?

Your files may not be lost. Your Xibo Docker installation, by default, stores your data locally on your machine, in folder named /shared. This is then mapped into the Docker containers as a ‘volume’. The file path of these volumes is stored within the ‘docker-compose.yml’ file you first configured for your setup and can be viewed by opening it with a text editor. Before making any further modifications to your setup, I would first confirm that the ‘shared’ folder is still there and contains the cms/library folder within it. If the folder is there, create a backup before making any changes to your setup. If you have changed the default locations of the volumes in your ‘docker-compose.yml’ file, then you should confirm that they are in the directory you have created.

The error you are receiving refers to the MYSQL_PASSWORD you have set in your config.env file. Have you made any changes to the config.env file?

Many Thanks.

Thank you for your response, i seemed to have resolved a part of the problem , initial location of xibo folder was C:Xibo\xibo-docker i changed this to C:Xibo. After this modification the error was no more.
I was experiencing an issue with xibo loosing all content, but this seems to be resolved for now, re-sharing the c drive in docker setting and stopping and restarting the containers brought back the settings. Thanks for the help.

Thank you for confirming, it’s great to hear you have solved the issue.

The behaviour you described suggested it may be related to the re-sharing the drive issue sometimes experienced by those using Docker on a Windows OS. I would still recommend making a manual backup of your Library just in case, this is of course up to you.

Many Thanks.

Yes, am using docker on windows 10 Enterprise 64 bit.
Yes sure will do a manual backup of folder.
Thanks again.

Best regards