When I reboot my host, docker ups a new instance of mysql, which overlaps the good one and as such shows and empty db:
[root@digital18 dockers]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a5d5cdde18d2 xibosignage/xibo-cms:release-1.8.6 "/entrypoint.sh" 6 days ago Up About a minute 0.0.0.0:80->80/tcp xibodocker_cms-web_1
7230b33ac43f mysql:5.6 "docker-entrypoint.sh" 6 days ago Up About a minute 3306/tcp xibodocker_cms-db_1
e5053c53b6a5 xibosignage/xibo-xmr:release-0.7 "/entrypoint.sh" 6 days ago Up About a minute 0.0.0.0:9505->9505/tcp, 50001/tcp xibodocker_cms-xmr_1
afebc9efc85e mysql:5.6 "docker-entrypoint.sh" 9 months ago Up About a minute 3306/tcp xibodocker183_cms-db_1
If I do stop everything, destroy the container xibodocker183_cms-db_1 and docker-compose start, it goes up correctly. But if I restart the node, the new mysql container is downloaded again.
How can I stop that?