Upgrade Xibo for Docker Install
- Xibo for Android
- DSDevices DSCS9X/95 Set-up Guide
- Install a White Label or a different Player version on DSDevices
- CEC Screen Power on/off with DSDevices
- Hardware Recommendations
- Philips Signage SoC Monitors
- Sony Bravia SoC
- Hisense Commercial Displays SoC
- Managing Storage on the Android Device
- Player Settings
- Players without an Internet Connection
- Remote Administration with SS Helper
- Restart Rooted Device with a Shell Command
- Running Xibo for Android
- Resolving Common Issues
- Error shown when I try to licence my Player?
- Player not updating from the CMS?
- I can see my Licence entry but the Player appears unlicensed?
- Error message - Player is missing dependencies
- My scheduled Layouts are not working?
- Layout won't play? Splash screen plays?
- Watchdog error message
- Troubleshooting for Administrators
- Audit Trail
- Log Information
- Player Logs
- Getting the Player Status
- Request Player Status via CMS - Logged in Players only
- Request Player Status directly from a Device
- Can I use the Xibo name / logo?
- Can I run a Xibo Player on Raspberry Pi?
- How can I increase the upload file size limit?
- How do Players communicate with the CMS?
- How many displays can Xibo support?
- How do I reset the Xibo_admin account password?
- Power On/Off for Players
- Testing with Xibo
- Why do I need a Default Layout?
- Xibo for Android FAQ's
- Autoplaying Embedded Youtube Videos
- Closing to Home screen
- Displaying Images
- Embedded TV
- External SD card not listed when running Banana-Pi
- Helper Command to change Time zone
- HTML5 Video
- Memory Notifications
- Menu not accessible
- SSL Support
- Using Portrait Displays
- Video wont play properly
Upgrade Xibo for Docker Install
Before attempting an upgrade
Please be sure that your media and database files are being correctly written to the shared directory. This is particularly important if you are running on a Windows computer. To do so, upload for example an image into the CMS, and check that the same image appears in the shared/cms/library directory. Another good check is to make sure that shared/backup/db/latest.sql.gz was created within the last 24 hours. If either of those checks fail, please do not proceed with the upgrade as this will lead to data loss. Seek support to recover the situation.
Before starting the upgrade, it’s strongly recommended to take a full backup of your Xibo system. So stop your CMS by issuing the command,
docker-compose stop
and then, backup config.env, your docker-compose files, and shared directory and keep them somewhere safe. On a Linux system, you will need to be the root user, or use sudo to make a copy of the shared directory.
If you’re upgrading from an earlier 1.8.0 pre-release, you may have previously used launcher. launcher was used for 1.8.0-alpha, beta, rc1 and rc2, but since then we have switched to Docker Compose. Further details are available in the 1.8.0-rc3 release notes.
Once you have a suitable backup of your CMS files, you can proceed with the upgrade process.
Upgrade Process
- Download the appropriate version of the Docker Compose files for the version of Xibo you want to upgrade to.
- Extract the Docker Compose files over the top of your existing installation, replacing any existing files.
If you are running the CMS on Custom Ports, then you will need to repeat the initial steps in the CMS installation process where you copied the template cms_custom-ports.yml.template file to cms_custom-ports.yml and make the appropriate modifications for the ports you want to use.
If you made any other changes to the docker-compose files, you will need to make those modifications again. config.env will have been preserved, so you should not need to make any changes there. Specifically, do not change the MySQL password in that file.
To perform the upgrade, run
docker-compose down
docker-compose up -d
substituting the second command there for the appropriate up command if you’re using custom ports or a remote MySQL server.
The CMS containers will be destroyed and rebuilt with the newer Xibo version.
A database backup will be automatically run for you as part of this process.
If you do see the upgrade wizard, you can attempt to work through it, however, please be wary of skipping upgrade steps unless you have a detailed knowledge that it is safe to do so.
The upgrade should now be complete for you.
Rolling back the Version
If you need to roll back to the older Xibo version for some reason, you can do so by running;
docker-compose down
restoring your original copy of config.env , the Docker Compose files and the shared directory, and finally running;
docker-compose up -d
The original version of the CMS will be restored for you.
