I have successfully installed the new 1.8 with the Docker image. It is also working. But, I have trouble to keep the settings and layouts and etc. If I just do a stop, and start (docker-compose stop docker-compose start), everything is still there. If I do a docker-compose down and then immediately the commando docker-compose up -d, it is restarting, but with a new, clean enviroment: all settings I’ve done are lost.
Also, as test, when I just do a docker-compose stop, and reboot the Windows 10 Machine (with all the updates every 2 weeks or so, this should be no problem to do that on a regular base), I also lost all settings.
In the documentation, there is written, you can safely do a down and after that a up -d command. But then I can start over again…
For the rest, when it is online, everything seems working. Also importing older layouts looks okay, only I need manually re-enter the [Date] in the layouts.
I assume here you’re running Docker for Windows (as opposed to Docker Toolbox)?
When your CMS is running, you should get a shared folder in the same directory as your docker-compose.yml file.
In that directory should be a cms/library directory which contains your media. If you upload a new file, does a new file appear there with your content in it?
If not, check that you have shared the hard drive your Xibo CMS files are on with Docker. To do so, right click on the Docker icon in the Windows system tray, and then go to Settings.
Then go back to the command prompt as before, and run docker-compose down, docker-compose up -d and then again upload a file and check that the file ends up in the CMS library as expected.
If it does, then that should resolve the issue. You can test by running docker-compose down, docker-compose up -d again and checking that your uploaded file is still shown in the media library.
With regard to reboots, there is a current bug in Docker for Windows that means that when you restart the machine, it may come up without correctly connecting to the shared directory (so it appears as if your content is lost). If that happens, simply running docker-compose stop, docker-compose start will resolve the problem. Hopefully this will be resolved quickly in Docker for Windows.
Hi Alex, thanks for the quick answer. The drive is shared indeed, I did forget that the first time, but then you’ll receive an error message when you enter the compose up -d command after a while.
I can also confirm, data is existing in the mentioned folder:
If I do a stop, start, everything is still there, so working great.
Now, I do compose down, and up -d command:
And even stranger, I saw this before, the Xibo site is not even accessible anymore:
