Default database after windows build update

Xibo was working fine until windows did a build update (windows 10 1803).

Xibo is now default (password and no content), when I look in C:\Xibo\xibo-docker\shared\cms\library all my content is there

in the past after a reboot i run:

cd Xibo
cd Xibo-docker
docker-compose.exe stop
docker-compose.exe start

and it was working again,

But now I get te message:

_docker-compose.exe : Starting cms-db … _
At line:1 char:1
+ docker-compose.exe start
_+ ~~~~~~~~~~~~~~~~~~~~~~~~_
_ + CategoryInfo : NotSpecified: (Starting cms-db … :String) [], RemoteException_
_ + FullyQualifiedErrorId : NativeCommandError_
_ _
_Starting cms-xmr … _
_Starting cms-web … _
e[2Ae[2KStarting cms-xmr … e[32mdonee[0me[2B
e[3Ae[2KStarting cms-db … e[32mdonee[0me[3B
e[1Ae[2KStarting cms-web … e[32mdonee[0me[1B
No containers to start

I tried updating Docker (version 18.03,1), restoring the database but this did not solve it.

Running docker ps -a

gives:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
aa1b2a0c6d93 xibosignage/xibo-cms:release-1.8.4 “/entrypoint.sh” 4 months ago Up 2 hours 0.0.0.0:80->80/tcp xibodocker_cms-web_1
7e1d5637ff9e mysql:5.6 “docker-entrypoint.s…” 4 months ago Up 2 hours 3306/tcp xibodocker_cms-db_1
224df7b107d1 xibosignage/xibo-xmr:release-0.6 “/entrypoint.sh” 4 months ago Up 2 hours 0.0.0.0:9505->9505/tcp, 50001/tcp xibodocker_cms-xmr_1

Does anyone have an Idee how to get it working again ?

I’d suggest reset docker to the factory defaults, re-share the C drive after that and then run the up command

Can I do that with out lossing all my work in Xibo ?

I did a factory default reset, and an Up and YES everything is working again :o)