CMS 4.3.1 upgrade to docker issue: no library sync

Get Help CMS Installation
1

To be completed by the original poster:

CMS Version

4.3.1

Installation Method

Upgrade from custom 4.3.1 to docker 4.3.1

Operating System

The operating system the CMS is installed on

Issue

The upgrade is a success. I used the cms_custom-ports.yml to first test on 8080 and then I switched to 80. Well, I encounter now one issue: subfolder shared/cms/library doesn’t 1) seems to have been copied in the container 2) is not in sync at all with the container.

For what I thought, this shared/cms/library folder should be the one were all my media are. I suppose this since in this page: Upgrade Xibo for Docker Install | Xibo Digital Signage , the first paragraph states that when you upload a file to the library using the web interface, I should get a copy at that place. When I upload a file, it is not, but I can find it in /var/lib/docker/overlay2/c6a462cfc2808cbd2f700ed81ab49a0a1bd9130316dc1b24fc9bd4dbbed1c0ea/diff/var/www/cms/web/shared/cms/library/ and /var/lib/docker/overlay2/c6a462cfc2808cbd2f700ed81ab49a0a1bd9130316dc1b24fc9bd4dbbed1c0ea/merged/var/www/cms/web/shared/cms/library/ . I’m not a pro of docker but it seems normal: I suppose this is the local fs of the container.

To solve my issue 1), I copied manually the files from my old media library to the one folder which stays when you docker compose stop . This seems to be a success: all media are now back to the displays.

I am using Debian Trixie and I believe my situation will be an issue if I try to upgrade to 4.4.0 . I didn’t found how the link between my docker install folder and the container should form. Can you help?

2

I’ve played a little more with docker. So, using docker inspect -f ‘{{ .Mounts }}’ contenairid shows that everything is find according to the volumes section of the yml file. Note that the contenairid is found using docker ps .

So I tried to docker exec -it contenairid /bin/bash and to create a file in my library: it is created on the host. Deleted from the host: it disappears from the contenair. So everything is fine.

Question is why at creation the library folder was not populated. I have only one idea: did I first create the container, then stop it, copy the files and restart it? In that case, does docker in this case skip the sync of the folders?

Anyway, it seems all good. I’ll consider that as closed.