Cannot stop container

So I’ve installed Xibo via docker on an AWS vm. It worked for a day and when going to update a layout I got:

Fatal Error - sorry this shouldn't happen. SQLSTATE[HY000] [2002] Connection refused

I followed an existing support thread (here) for it suggesting to take the container down clear the files and bring it back up fresh but get this when trying to docker-compose down.

Stopping xibo_cms-web_1 ... error
Stopping xibo_cms-db_1  ... error
Stopping xibo_cms-xmr_1 ... error

ERROR: for xibo_cms-web_1  cannot stop container: c3a2e22bd45e60f72d1c88919147c63c65a79ccb9e133a6ddee13b637f01b5a7: Cannot kill container c3a2e22bd45e60f72d1c88919147c63c65a79ccb9e133a6ddee13b637f01b5a7: connection error: desc = "tran sport: dial unix /var/run/docker/containerd/docker-containerd.sock: connect: connection refused": unknown
Removing network xibo_default
ERROR: network xibo_default id 47d24acf2f7fd6480f8e0752edfa68ca2464df523fe30daf1e0941a16113ecc8 has active endpoints

I’ve not seen that before - it looks like the docker daemon has stopped for some reason - you could try restarting it

service docker restart

I should have thought to check that… Thank you.

Now if I bring the container backup without removing the shared directory it should pull my library and layouts back in right?

Answering my own question in-case anyone has similar issues, but yes you can bring it up and it has everything still.

1 Like

Absolutely - the database and cms store their state and files in the shared folder for this purpose. As long as you have the shared folder, you can get back to a working CMS.