SixK
commented
1 year ago not sure of all I'll say. Luckily, you probably only destroyed containers content. (binaries/sources of applications) data are stored in volumes in your case /opt/docker/volumes (and probably /opt/docker/volumes/coco-annotator_mongodb_data/ for mongo database) images dataset are stored in datasets directory located in your coco-annotator sources directory. If you already did some export of your coco-annotation, you may have some .exports/ directories that you could import. (located in datasets/yourdataset/.exports)
Well, you probably only have to build coco-annotator images again using "docker-compose -f docker-compose.build.yml build" For permissions problem, I dunno if simply using sudo could help ? Before doing anything, first backup you /opt/docker/volumes/ mongo db volumes first. If docker-compose don't find your volumes, first try to see if volume name has changed. You'll may have to copy your mongodb files to the new mongodb volume (after having stopped mongodb)
So I had an issue where a logfile grew too much that caused my containers to crash.
I located the 64G log file in /opt/docker/containers and deleted it.
My COCO-annotator was still down through the broswer so I ran "docker-compose up", to which I got:
ERROR: for annotator_mongodb cannot stop container: 01171a841... : permission denied
So I ran a "docker rm -f 01171a841" but got: Error response from daemon: Could not kill running container 01171a841... , cannot remove - permission denied
So I ran "docker-compose start" but I had to create account again and lost all datasets and annotations. Is there a way to recover?
I now know that deleting the mongo container was a bad idea. But I wasn't even allowed to remove it, so it should all still be there. Any ideas?