The collection path is has changed (contains the aufs for docker) for details, see URL Reproducible: Always Steps to Reproduce: 1. start docker 2. start digikam Actual Results: all pictures are gone, metatdata gone Expected Results: all pictures are still there stopping docker and restarting digikam helps, but then digikam has to reindex everything
Docker.IO is a very specific run-time environment, never tested... Gilles Caulier
Maybe I wasn't clear enough: I'm not talking about running digikam inside docker or using any docker features. I just installed docker on my desktop PC where I'm also running digikam. My setup: - Kubuntu - installed digikam, added pictures, ... - apt-get install docker.io -> digikam stops working (uses wrong path) I have no idea why digikam even changes the storage path. When I run "service docker stop" and start digikam afterwards, it works again.
No idea. It sound like more a DOWSTREAM problem to report on Kubuntu team. We have nothing to deal with docker.io Gilles Caulier
The problem is not within docker. The problem is that digikam determines the collection path in a wrong way.