Okay, for starters I can see that the system was once started with the service name xibo-docker and another time with the name xibodocker. By default I believe that docker-compose utilizes the name of the containing directory. Did you rename the directory at some point? If so, just know that doing so will have an adverse effect on the function of the commands and will require manual intervention.
Now to get things back online… Go ahead and remove all of the containers. If you aren’t running anything except for Xibo, then you can remove all stopped containers with this command:
docker container prune -f
Because your configurations and media are all stored in volumes, nothing should be lost by removing the containers. You should now be able to start everything from scratch, and any ports held by the stopped containers will have been released:
docker-compose up -d
My only concern here is that your containers exited in the first place, but I’m confident that this will get you back online.