View Single Post
Old 03-25-2023, 10:55 PM   #2
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,708
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
A very bad idea. Sharing data from within a Docker container is not fun even after you have the Docker volumes setup. If you had your calibre instance installed in Linux, accessing a calibre database from two calibre instances is a great path to database corruption. If you were using calibre installed in Linux, you might be able to get away with this for a while sharing the calibre library over the network and making sure that one calibre instance was shutdown before the other was started. Even there, you are likely to run into the issues with running calibre with it's database on a network share.

And yes, people have gotten away with this for fairly long times. Then they show up here whinging that my database has problems, my libraries have disappeared, etc.

Last edited by DNSB; 03-25-2023 at 10:58 PM.
DNSB is offline   Reply With Quote