Upgrade from 3.0.5 non docker-compose, to 3.1.0

CMS Version


Installation Method

Docker without Docker-compose

Operating System

Synology DSM 7.0.1-42218 Update 2


Could anyone provide clean and straightforward instructions how to upgrade from version 3.0.5 to 3.1.0, step-by-step? I have no much knowledge of Linux systems nor Docker internal workings, however I followed this tutorial (Synology DSM6+ - Xibo Docker 1.8+ Installation) and got the 3.0.5 version up and running approximately 1/2 year ago. There was no docker-compose involved as I had no knowledge of its existence and importance.
I tried official, docker-compose, route now, however it, of course seems not to have any knowledge of the previous installation in the ‘down’ step, so it leaves the previous installation where it is up and working. The ‘up’ step completes for the most part of it, bringing up the new, paralell, installation, however it fails for the ‘db’ part of it:

Creating xibo-docker-310_cms-quickchart_1 …
Creating xibo-docker-310_cms-xmr_1 … done
Creating xibo-docker-310_cms-db_1 … error
Creating xibo-docker-310_cms-quickchart_1 … done

ERROR: for xibo-docker-310_cms-db_1 Cannot start service cms-db: Bind mount failed: ‘/volume1/docker/xibo-docker-3.1.0/shared/db’ does not exists

ERROR: for cms-db Cannot start service cms-db: Bind mount failed: ‘/volume1/docker/xibo-docker-3.1.0/shared/db’ does not exists
ERROR: Encountered errors while bringing up the project.

The previous (3.0.5) installation looks like this:


The original documentation you followed as far as I can tell has been provided by an end-user (cslaughter) who somehow managed to get this working on his synology nas unit.

I too am an end-user I don’t have a synology drive running the cms, however looking through the document and the comments afterwards, he states not to use the normal upgrade procedure but rather first to make sure you have a full backup, then go into the docker control panel and shutdown the old container, change some settings of the old container so they don’t clash with the new one, including renaming them, then install the new container using the original settings that you used 6 months ago, and fire up the new container (as far as i can tell this new one will still point to your original cms-db), however probably better reading the original posters comments yourself.

A link to his comment on upgrading and 3 responses from others relating to upgrading.

Just in case the link doesn’t work look for a comment in the instructions you followed, the comment is dated July 2017.

Hope that helps.

I’m just an end user too so very unlikely to be able to help further, cslaugher might though.


This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.